This article explains how to set up SAML 2.0 single sign-on in Personio. SAML (Security Assertion Markup Language) 2.0 is a widely used authentication standard. With this setup, your organization can use an existing identity provider (IdP) to log in to Personio. This means that your employees don’t need to manage a separate Personio password.
Personio supports any IdP that complies with SAML 2.0, including:
- Microsoft Entra ID (Azure AD) / ADFS
- Okta
- OneLogin
- JumpCloud
Before you start
- To set up SSO with SAML, you need the following permissions:
- An Administrator role in Personio, or
- An employee role with edit permissions for Account configuration > Authentication.
- Make sure you’ve already invited your employees to Personio. They each need to activate their account before they can log in.
- You need admin access in your IdP to register a new service provider application.
- Your IdP must support SAML 2.0 with service provider-initiated SSO.
- Personio matches authenticated users to employee records by email address. Every employee who uses SAML SSO must already have an employee profile in Personio with a matching email address.
Step 1: Open the SAML configuration in Personio
Follow these steps:
- In Personio, go to Settings.
- In the Security & integrations section, click Security & authentication.
- From the list of login methods, go to SAML and click Configure.
- Under Provider settings, Personio displays a number of metadata fields and preset values. You need these values in the next step when registering Personio in your IdP. The following table lists each metadata value and what to do with it.
| Field | Details |
| Assertion Consumer Service (ACS) URL | The endpoint where your IdP sends the SAML response after a user authenticates. |
| Identifier (entity ID) |
A globally unique identifier that represents Personio in your SAML federation. |
| Signing certificate (optional) |
A certificate used to validate signed SAML authentication requests. All authentication requests from Personio are signed using RSA-SHA256 and sent via HTTP-POST. Download the certificate, as you’ll need it for the next step. You can select either .cer or .pem format, depending on your needs. |
Step 2: Register Personio as a service provider in your IdP
Using the Provider settings values from Step 1, register Personio as a new SAML application in your IdP. The exact steps depend on your IdP, but you typically need to:
- Create a new SAML application in your IdP (sometimes called an Enterprise Application, Relying Party Trust, or Service Provider connection).
- Set the Assertion Consumer Service (ACS) URL / Reply URL to the Personio values from Step 1.
- Set the Entity ID / Identifier to the Personio Entity ID from Step 1.
- Optional: Upload Personio's signing certificate (downloaded from Step 1) so your IdP can verify signed requests.
- Configure your IdP to send the user's email address as an attribute. Personio identifies the employee by checking for an email attribute in this order: a standard email claim (for non-Microsoft IdPs), then http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress, then http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier. This address must match the employee record in Personio to grant access.
- In your IdP, set the Name ID format to Email address. This ensures your IdP sends the user's identity in the format Personio expects. Without this, employees may see an error when trying to log in.
- Once saved, locate your IdP's SAML metadata address. This is typically found in your IdP's application settings under a label such as App Federation Metadata URL, SAML Metadata URL, or Federation Metadata endpoint. Copy this address, as you need it in the next step.
Step 3: Complete the configuration in Personio
Return to the SAML configuration page in Personio. Fill in the following fields.
Configuration
| Field | Details |
| Metadata .xml URL | The SAML metadata address from your identity provider. Personio uses this to automatically retrieve your IdP's signing certificate, SSO endpoints, and other settings. |
Login experience (optional)
| Field | Details |
| Button display text |
Enter the text you want to appear on the login button, for example, “Continue with [your text]”. Note that custom text isn’t translated. If you leave this field empty, the login button displays "Continue with SSO" by default. |
| Home Realm Discovery |
Enter one or more email domains separated by a comma. The system automatically routes users with those domains to this IdP at login. For example, enter yourcompany.com if your employees use @yourcompany.com email addresses. This setting is most useful if you’ve also enabled Personio Credentials. It forces users with matching domains to log in via SAML, rather than with their email and password. |
Step 4: Save and test the connection
Tip:
If you plan to set your chosen IdP as the only enabled login method, perform a configuration test first. This prevents you from locking yourself out if the configuration is incorrect.
Make sure you’re logged in as an admin while testing the connection. Your Personio account email must match a user in your IdP. If the test fails, verify that the ACS URL and Entity ID in your IdP exactly match the values Personio provided in Step 1. Even a small difference (such as a trailing slash) causes the connection to fail.
- Review the data you've entered in Personio.
- Click Submit to save your configuration. Personio contacts your IdP's metadata address and imports the signing certificate, SSO endpoints, and other IdP settings.
- Review the imported IdP details: the sign-in address, the certificate common name, and the certificate expiry date. This helps ensure that you’ve connected the correct IdP.
- Test your connection.
During the test, Personio initiates a SAML authentication flow that redirects you to sign in with your IdP. It returns you to the same page on success, which confirms the connection is working.
Understand login behavior after configuration
Once SAML SSO is active:
- Personio-initiated login only: Employees must start via the Personio login page. Logins initiated directly from the IdP dashboard (IdP-initiated SSO) aren’t supported.
- With Home Realm Discovery: If an employee’s email address matches a configured domain, the system automatically redirects them to the IdP login page.
- Without Home Realm Discovery: Employees click the SSO login button on the Personio login page. This redirects them to your IdP. If they enter their email address in the email field instead, they're prompted for a password rather than redirected to your IdP.
- Employee matching: After authentication, Personio matches the user to an employee record by email address. If no matching record exists, access is denied.
Update your IdP metadata
Tip:
Personio doesn't automatically detect changes to your IdP's metadata. If you change your IdP configuration, you need to re-sync manually using the steps below.
If your IdP's signing certificate is renewed or your IdP configuration changes, you can update the metadata in Personio. You can do this without reconfiguring the connection.
- Go to Settings.
- In the Security & integrations section, click Security & authentication.
- From the list of login methods, go to SAML and click Manage.
- In the Configuration section, go to the field Metadata .xml URL and click Update.
- Enter the metadata address.
- Save your changes.
Personio re-syncs with the metadata address and updates the certificate and endpoint information. You can see the certificate expiry date after you save your changes.
Understand SAML security settings
The following security settings apply to all SAML connections in Personio. You can’t change them. The following table lists each setting and its value.
| Setting | Value / behavior |
| Request signing | All SAML authentication requests sent by Personio are signed by default. Configure your IdP to accept signed requests. |
| Signing algorithm | RSA-SHA256. SHA-1 is not supported. |
| Request binding | HTTP-POST is enforced. HTTP-Redirect is not supported. |
| Assertion validation | Handled by Auth0 (Personio's identity layer), which validates SAML assertions, certificates, and signatures. |