Introduction

By integrating your Docebo learning platform with Gmail, you can bind your Docebo user profiles with their corresponding Gmail accounts. This way, every user inside your platform can sign into their Docebo platforms without needing to manually enter the credentials. This manual will show you the integration in both your Docebo learning platform as well as from Gmail's side.

Important Notes about Docebo for Gmail

• The Gmail integration with Docebo only works with Gmail accounts. You cannot use your Google Apps Developer account for this integration.
• In order for your users to be able to log in to their learning platforms with their Gmail credentials, their Gmail addresses must correspond with an email address registered in Docebo. Then, your users can log into the platform by pressing the Gmail icon on the platform's sign-in page.

Activating the Gmail App in Docebo

Activate the Gmail app as described in the Managing Apps & Features article of the Knowledge Base. The app is listed in the Single Sign On tab.

Once it’s activated, you can begin the configuration. Please refer to the section below to learn more.

Configuring the Integration

Begin by logging into your Docebo Learn platform as a Superadmin and press the Admin Menu icon. Next, locate the Gmail section and press Manage.

In the Google SSO screen, copy the Redirect URL and paste it into a text editor, such as Notepad, for later use.

Next, log into your Gmail account and then visit the Google Cloud Services API Console (opens in a new tab). Once you're on the Google APIs console, click the Create Project link in the Dashboard screen.

Enter the Project name, select the Organization from the drop-down menu and choose the Location, then press the Create button.

Now, in the resulting screen, from the left sidebar, choose the OAuth Consent Screen tab.

On the following screen select Internal for the User Type and press the Create button.

In the next screen, in the App information section, give your app a meaningful name and pick the support email address from the drop-down menu in the User support email box. Next, move to the App logo section and, optionally, upload a logo file for your app.

Move to the Authorized domains section and press the Add Domain button to reveal the Authorized domain 1 text box. There, enter the domain name of your authorized domain. Next, in the Developer contact information section, select the Email addresses text box and enter a developer email address. Then, press the Save and Continue button.

Next, in the Scopes screen, scroll down and press the Save and Continue button.

In the resulting Summary screen, scroll down and press the Back to Dashboard button.

Now you can create your Client ID. Click on the Credentials tab. Then, at the top of the resulting Credentials screen, click Create Credentials.

In the resulting drop-down menu, select OAuth client ID.

In the following screen, select Web Application from the Application Type drop-down menu.

Next, in the Name text box, give your Web Application a meaningful name. Move to the Authorized redirect URIs section and press the Add URI button.

Enter the Redirect URL you copied into a text editor earlier into the URIs 1 text box, then, in the Authorized JavaScript origins section, press the Add URI button. In the URIs 1 textbox, enter the URL of your platform. If you are using a custom domain, insert the custom domain URL. Next, press the Create button.

Next, you will be presented with your Client ID and Client secret. Copy these items to a text editor so you can paste them into the Docebo for Gmail administration screen.

Next, return to the Docebo Learn platform and access the Administration screen for Gmail. In the Consumer Key field, paste the Client ID value you copied into your text editor earlier. In the Consumer Secret field, paste the Client secret value you copied into your text editor previously.

Next, press Save Changes to complete the integration process. You can find your Google credentials on your Google Admin Console in the Credentials tab whenever you need them.

Best Practices

When an SSO integration and a custom domain are set up at the same time, it is strongly suggested to configure the Custom Domain first. The endpoint URLs needed for the SSO integration are dependent on the URL of the platform.