Below are the details on how to integrate Namely and Engagedly, in order to meet both the prior scenarios.

Note: Before beginning the integration process, make sure you are a ‘Site Administrator’ in Engagedly and are an ‘Administrator’ in Namely as well.

Syncing Users from Namely

Log into Engagedly as Site Administrator then navigate to Settings > Integration (under Organisation Section) > Namely.

Log into Namely as an Administrator then click on API from the header dropdown. If you do not get the API link, please contact Namely for further assistance.

Now in Namely, you have to create a permanent access token. To do that fill the input field with the name ‘Engagedly’ under ‘New Permanent Access Token’ section and click Create.

The above action will create an access token. The access token is only visible for a short period of time, so make sure you copy the access token first.

Then switch to Engagedly and go to the Namely Integration page. Paste the access token you copied beside the field Access Token, check ‘Enable Sync Users’ and fill the Organisation Subdomain field with the subdomain of your organization in Namely. Then, save the settings.

On saving the setting, a button ‘Sync User’ will appear on the bottom left corner of the form. Click the button to sync users. If all the settings are fine, Engagedly will start syncing the users. If not, you will receive an error message.

Single Sign On With Namely

Log into Engagedly as the Site Administrator, then navigate to Settings > Integration (under Organisation Section) > Namely. Copy the Redirect URL. We will be needing it.

Log into Namely as Administrator then click on API from the header dropdown. Now in Namely, you have to setup an OAuth2 application. To do that, click New Application under Your OAuth2 Applications.

Now fill up the form as:

Name: Engagedly

Website: https://engagedly.com

Redirect url: URL copied earlier on from Engagedly

Then click Submit.

The above action will create a new OAuth2 application. Click on to the Application and copy the Client Identifier and Client Secret.

Now go back to the Engagedly Namely Integration page. Paste the value of Client Identifier beside label Client Identifier and Client Secret beside label Client Secret, check Enable SSO, and fill the Organisation Subdomain field with the subdomain of your organization in Namely, then save the settings.

You have successfully delegated the authentication process of Engagedly to Namely, do not forget to have a test run before trying anything.