Identity, Access & Data Control

With single sign-on, people sign in to Pagination with their company email and the credentials managed by your IT department. There is no separate Pagination password to create, share or forget.

Single sign-on works with the identity providers most companies already use:

• Microsoft Entra ID (formerly Azure Active Directory)
• Okta
• Google Workspace

Other identity providers can be connected too, with the setup checked directly with your IT department.

• SCIM provisioning: accounts are created, updated and deactivated automatically from your directory, with no users to manage by hand in Pagination.
• Your sign-in policies apply: multi-factor authentication and password rules stay under the control of your IT department.
• Set up with your IT team: the Pagination team agrees the configuration directly with the people who manage your identity provider.

Single sign-on and SCIM are available for enterprise accounts.

Shared logins are the weak point of many tools adopted by a single team. A password passed between colleagues is rarely changed: Pagination hardly ever receives a password change request for a shared account. When one of those colleagues moves to another company, nobody can be sure their access has ended.

• With single sign-on and SCIM: when your IT department disables a person in your directory, that person can no longer sign in to Pagination and their account is deactivated automatically.
• Named users instead of shared logins: one account per person, so every sign-in can be traced to someone.
• User packages: multi-user packages cost much less per person than single accounts, so giving everyone their own login does not have to raise the bill.