DigitalChalk allows you to add social site integration to your DigitalChalk site.  If you have the right permissions for your organization, you can add one, some, or none of these social applications to your site.  Currently DigitalChalk supports Facebook, Twitter, Google+, and LinkedIn login integrations. All login integrations use the industry standard OAuth2 protocol.  (Note: Twitter supports OAuth 1a only)


  •  You must have Organization Administrator rights to your DigitalChalk site
  • You have an application set up on the associated social site.  To do this, you will need a developer account on each social site that you wish to use.  Each social site has its own method of doing this, but we have written short guides on doing this on the most popular:


If you have Organization Administrator rights on your organization’s DigitalChalk site, you can configure your site to use social site integration.  You do this on the Administration > My Organization > Social Apps page.

Clicking on the “Social Apps” menu will bring up the following screen:

On this screen, you will see all the supported social applications and whether or not you have configured them for your site.  In the above example, we have configured 3 social apps, but Twitter has not been configured.  To edit an application, simply click on its logo (or for new apps, you can also click on “Enable”).  Let’s click on the Facebook icon and look at the edit page.

Here you can modify your application ID, secret, and namespace (which all come from Facebook itself).  You can also toggle whether students can login with Facebook (the Yes / No option in the screenshot above).  Setting login to “Yes” will cause the Facebook logo button to appear on the login page.

Most services* also have three other options (which are visible above):

  • Auto Create User : If a user logs in with Facebook (or other service), but we can’t match their account in DigitalChalk by their email address, then automatically create a new DigitalChalk user for them and attach this social account
  • Auto Match Email: If a user logs in with Facebook (or other service), and their Facebook email matches a DigitalChalk student’s email, automatically link the two accounts
  • Restrict to Domain: If this is set, the student’s email address on the social site must match the domain listed here.  For example, if you only want people with @digitalchalk.com email addresses to be able to login with Facebook, set this field to “digitalchalk.com”.  If this field is blank, then any student email address is accepted.

*Please note that the options above are not available for all social sites.  Notably, Twitter does not allow access to a Twitter user’s email, so these options are not available.

Application ID, application secret and application namespace must be supplied by the associated social site.  For example, in the above screen, the application ID, secret and namespace must be assigned by Facebook.  We have guides for each setting up applications on each of these platforms:

If you decide not to allow student login with a particular service, you can set the allow login switch to “No” above.  DigitalChalk will remember the application parameters.  This is handy if you are testing a new social application.  Alternatively, you can click on the “Disable” link in the social apps list, and DigitalChalk will delete any information about the app from the system (you can always add it back in later).