Security Rules: Single Sign-on
Updated over a week ago

Single sign-on works by offloading the authentication of a reader to your single sign-on login screen, before redirecting them back to PageTiger.

๐Ÿ’ก Example
If your organisation uses Office 365 single sign-on, your staff will login in there first before gaining access to your document.


There are several benefits to using single sign-on:

  • No need for a separate PageTiger reader account.

  • No need to sign in if you are already logged into your single sign-on login screen.

  • Track and monitor the reader interaction within your document.


There are many different single sign-on standards, although SAML is preferred by the majority of our customers.

We support the following standards:

  • SAML 2.0*

  • OAUTH2



We can integrate with:

  • ADFS

  • Azure AD/Microsoft Office 365

  • Okta

  • Google

  • Salesforce

  • Shibboleth

  • WSO2

  • OneLogin

  • Bitium

  • Centrify

*The SAML 2.0 authentication journey


The configuration of single sign-on is set-up by the PageTiger technical team - please contact your Account Manager for more information and they will ensure you are on the correct service charge to enable the feature.

Applying SSO to your document

To apply the security rule to your document, navigate to it and select the Security Rules tab, followed by the rule that has been set-up for you.

Session Timeout warning

The document viewer will be logged out after 60 minutes of inactivity for protected documents. After 58 minutes of inactivity the viewer will be shown a popup message with a countdown indicating that their session will time out in 2 mins. If they click the continue button their session will stay active for another 60 mins. If they do not, they will be logged out once the countdown reaches 0 and be shown a message with a button to login again.

Did this answer your question?