ℹ️ Available on all plans.
With Single Sign-On (SSO), your users log in to Perdoo with the account they already use at work, so they don't need another password. It also keeps your account more secure. SSO works in the mobile app too.
You can use Google, Microsoft, or Apple on all plans. SAML, for example with Okta, OneLogin, or Microsoft Entra ID, is available on Premium and Supreme.
Set up SSO
ℹ️ This requires Superadmin rights.
Go to Configure > SSO.
Select Enabled (1).
In Company domain(s) (2), enter your company's email domain. To add several, separate them with a comma.
Optionally, select User provisioning (3). Perdoo then creates a user when someone with your domain logs in for the first time. Without it, only existing users can log in.
Choose the Default role for users created through provisioning (4), for example Standard.
Optionally, select Strict authentication (5). Users can then only log in through SSO, not with a password.
Choose your Provider (6): Google, Microsoft, Apple, or SAML. For SAML, fill in the fields below. See Set up SAML.
Click Save.
Set up SAML
ℹ️ Available on Premium and Supreme.
Go to Configure > SSO and choose SAML as the Provider.
Copy the Service Provider ACS URL (5) and the Service Provider Entity ID (6) to your identity provider.
From your identity provider, copy the Entity ID (1) and the SSO URL (2) to Perdoo. Optionally, add the SLO URL (3).
Click Reveal next to IdP Certificate (4) and paste your identity provider's certificate.
Click Save.
Perdoo supports these SAML attributes:
First name: user.first_name.
Last name: user.last_name.
Job position: user.job_position.
To sync more details, such as managers and teams, use SCIM provisioning.
Set up SAML with Microsoft Entra ID
ℹ️ Available on Premium and Supreme.
In Perdoo, go to Configure > SSO, select Enabled, and choose SAML as the Provider.
Go to the Azure portal.
Under All services, search for and select Enterprise applications.
Click New application.
Click Create your own application.
Give it a name, for example Perdoo, and click Create.
Go to Single sign-on and select SAML.
Under Identifier (Entity ID), enter
https://api-eu.perdoo.com/metadata/.Under Reply URL (Assertion Consumer Service URL), enter the Service Provider ACS URL from Perdoo, and click Save.
Copy the Login URL to the SSO URL field in Perdoo.
Copy the Microsoft Entra Identifier to the Entity ID field in Perdoo.
Go to Attributes & Claims and set the Source attribute of the Unique User Identifier (Name ID) to user.mail. Keep the default attributes.
Download the Certificate (Base64) and open it in a text editor. Copy its contents to the IdP Certificate field in Perdoo, and click Save.
Under Users and groups, add the users or groups who should get access. Then test the connection.
Good to know
Do user details update in Perdoo when they change in our identity provider?
Not with SSO. Perdoo only copies a user's details when it creates the user. To keep details, managers, and teams in sync, use SCIM provisioning.
Why do I get a Server Error (500) when I log in with SAML?
Check the email address for typos.
The email address may already be used by another Perdoo account.
You may not have been added to your company's Perdoo account yet. Ask your Superadmin.
Check with your identity provider that your user details are correct.
Why do I get error AADSTS50105 when I log in with Microsoft Entra ID?
You haven't been given access to the Perdoo app in Microsoft Entra ID. Ask your Azure administrator to add you:
In the Azure portal, go to Microsoft Entra ID > Enterprise applications.
Search for Perdoo and open it.
Go to Users and groups and click + Add user/group.
Select the user and click Assign.
For more information, see Microsoft's guide.
Need help?
Start a live chat with our Support team by clicking the question mark at the left or right bottom of your screen.