Docebo
Connect Docebo to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Docebo to collect security training evidence with automated compliance tests, switched on per workspace.
| Category | Security Training |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Docebo's guide | help.docebo.com |
Connect with an API token
-
In Docebo:
- Sign in to Docebo as a Superadmin. If the API and SSO app is not active yet, activate it from Apps & Features (vertical tab Docebo Additional Features).
- Click the gear icon in the top right to open the Admin menu, find the API and SSO section and select Manage.
- Open the API Credentials tab and click Add OAuth2 App.
- Fill in the app name and description, set the Client ID, note the auto-generated Client secret, enter a Redirect URL, check the grant types (click Show advanced settings if needed) and click Confirm.
- Activate the app by clicking its checkmark icon (it turns from grey to green).
- Get an access token for the API with scope api from https://<subdomain>.docebosaas.com/oauth2/token using that client. Alternatively open https://<subdomain>.docebosaas.com/api-browser/, click OAuth on any endpoint, click Authorize, click Authorize again in the Authorization required dialog, and copy the token from the Token field.
Where to find the other values:
- Subdomain: Your platform address, https://<subdomain>.docebosaas.com; enter the part before .docebosaas.com.
Docebo's public documentation does not cover every step.
Source: developer.docebo.com, developer.docebo.com, developer.docebo.com, help.docebo.com, checked 2026-10-07.
The permissions Safeguard needs:
api,users and enrollments: read. -
On Compliance › Connectors, open Docebo, click Connect, choose API token and fill in:
Field What to enter Subdomain Required. The part before .docebosaas.com in your address. Access token Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Docebo and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | CC1.4, CC2.2 | 1 |
| ISO/IEC 27001 | Automated tests | A.6.3 | 1 |
| HIPAA Security Rule | Automated tests | 164.308(a)(5) | 1 |
| PCI DSS | Automated tests | 12.6.1 | 1 |
| NIST CSF 2.0 | Automated tests | PR.AT-01 | 1 |
These tests are switched on per workspace by the Safeguard team.
Related
- Security Training connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks