Single sign-on (SSO)

With single sign-on (SSO), your team signs in to the Notabene dashboard with the accounts they already have in your company’s identity provider, such as Okta or Microsoft Entra ID. An admin at your company sets it up once, in a guided setup that Notabene sends as a link.

SSO covers the people who use the dashboard. Your backend keeps calling the API with an API credential and access tokens, as described in Authentication.

Identity providers

If the setup does not list your provider with the type you use, choose Generic SAML or Generic OIDC.

Setup

Your admin needs the rights to create applications in your identity provider and to assign users and groups to them.

1. Ask for the setup link. Write to [email protected] with the name and email address of your admin, and Notabene sends them the link.
2. Choose your identity provider in the setup.
3. Create an application for Notabene in your identity provider, with the values the setup shows for that provider.
4. Connect it by entering your email domain and the application’s details in the setup.
5. Map the user attributes the setup lists, such as the email address, to the fields of your identity provider.
6. Assign the application to the users or groups who will use the dashboard.
7. Test the sign-in in the new tab the setup opens, then finish the setup.

From then on, the people you assigned sign in to the dashboard through your identity provider. The link is valid for up to 5 days, and once your admin opens it, the setup must be finished within 5 hours, so ask for a new link if either runs out.

Changes to the connection

To change the connection later, for example to replace a SAML certificate before it expires or a client secret you rotated, ask Notabene for a new link. It opens the same setup on your existing connection.