IntegrationsSingle sign-on and SCIM
One company login. Accounts that follow your directory.
Office staff sign in with the account they already have. Staff without a company address keep signing in with an email code.
Works with
Microsoft Entra ID
Google Workspace
Okta
OpenID Connect- SAML 2.0
- Directory Sync (SCIM)
Ready for the security review
- 01
Your provider, your rules
Passwords and multi-factor sign-in stay with Entra, Google, Okta or any OpenID Connect or SAML 2.0 provider.
- 02
Leavers lose access
With Directory Sync (SCIM), your directory creates, places and disables accounts, so access follows your people list.
- 03
Nobody locked out
Require single sign-on for your company domain. Contractors and staff on other addresses keep their email code.
Set up in four steps
- 1
Connect your provider
For Microsoft Entra ID and Google Workspace, an admin approves Aristotl. For Okta, OpenID Connect and SAML 2.0, a guided page walks you through registering Aristotl.
In the app · Settings › Integrations
- 2
Verify your domain
Prove you own your email domain with a DNS record, so only your staff are sent to your company login.
- 3
Test, then turn on
Try a test sign-in first. Sign-in only switches over once the test passes.
- 4
Add Directory Sync
Optional: create a SCIM token and add it to your identity provider. From then on, your directory creates and disables accounts.
What changes
| Today | With Aristotl |
|---|---|
| One more password for staff to forget | The company login they use every day |
| Leavers keep access until someone remembers | Disabled in the directory, disabled in Aristotl |
| IT registers apps and copies secrets | Approve Aristotl for Microsoft or Google sign-in |
Questions about single sign-on
More integrations
All integrations
Ready when you are
Bring your IT team to the demo.
We'll walk them through sign-in, provisioning and data handling in a 30-minute call.