Connect company sign-in
Let members sign in with your identity provider, test it first, and set who can sign in and how.
Company sign-in lets members use their work account, through any OpenID Connect identity provider. Set it up under Organisation settings › Sign-in.
Register the portal with your identity provider
Create a web application (OpenID Connect, authorisation code) with the redirect URI shown on the Sign-in tab.
| Provider | Issuer URL | Groups for roles |
|---|---|---|
| Microsoft Entra ID | https://login.microsoftonline.com/<directory id>/v2.0 | Add a groups claim; map the group object ids it sends. |
| Okta | https://<your-org>.okta.com | Add a groups claim named groups to the ID token. |
| Google Workspace | https://accounts.google.com | No groups: give roles under Members. |
| Keycloak | https://<host>/realms/<realm> | Add a Group Membership mapper named groups to the ID token. |
Turn it on
- Enter the Issuer URL, Client id and Client secret. Change Groups claim and Scopes only if your provider needs it.
- Turn Sign-in on and choose Save.
- The first time, the portal keeps sign-in off and asks you to Run a test sign-in before turning it on. Choose Test sign-in and sign in with your company account.
- Back on the tab, it says Test sign-in worked. Turn Sign-in on again and choose Save.
The test proves the settings, so nobody gets locked out. The secret is stored encrypted and never shown again.
Who can sign in, and how
Who can sign in, and how, at the top of the tab, applies from each person's next sign-in.
- Ways to sign in: untick any of password, Google, Microsoft or GitHub your organisation shouldn't use.
- Require company sign-in for your email domains: people at your domains must use your identity provider; guests can still use the other ways. Turn it on while signed in with company sign-in.
- People with a confirmed email at your domains: Join only when invited, or join automatically as a viewer, designer or publisher.
- Require two-step verification for publishers and admins: for password and social sign-in. Until they turn it on, they work as designers. Set it up for yourself first (Two-step verification).
- Sessions: sign out after inactivity (5 to 480 minutes), the longest session (up to 168 hours), and sessions at once per person. Empty uses the portal's limits: 8 hours idle, 7 days at most.
If something goes wrong
| What you see | What to do |
|---|---|
| "The issuer's discovery document couldn't be read" | Check the issuer URL: it must publish /.well-known/openid-configuration. |
| Set by the server | This portal's company sign-in is set by IT. Ask them to change it. |
| The test sign-in fails | Check the redirect URI, client id and secret in your identity provider, then test again. |
| Nobody can sign in | On a hosted portal, ask the operators to fix sign-in or add an admin. Otherwise ask IT. |