Single Sign-On (SSO) lets you access Document360's Knowledge base portal using your existing credentials from a trusted Identity Provider (IdP) such as Okta, Azure AD, or Google Workspace. Instead of maintaining a separate Document360 password, you authenticate through your organization's IdP and are granted access automatically. This applies to projects where SSO has been configured using SAML or OpenID Connect.
Before you begin
- SSO must already be configured for your project by an Owner or Admin. If SSO has not been set up, contact your project administrator.
- Your email address must match the domain specified in the SSO configuration.
- You need the Knowledge base portal URL for your project.
How to log in to the Knowledge base portal using SSO
-
Open your web browser and enter the URL of the Document360 Knowledge base portal you want to access.
-
In the Email or Subdomain field, enter your email address or subdomain name.
SSO users now require login via subdomain to support scalability improvements. This applies to all new or updated SSO configurations. Email-based login is no longer supported.
- Click the Continue with SSO button.
- You will be redirected to your IdP's login page. Enter your credentials to authenticate.
After successful authentication, you are automatically logged into Document360's Knowledge base portal.
IdP-initiated sign-in
If the Allow IdP initiated sign-in option was enabled during SSO configuration, you can log in to Document360 directly from your IdP's dashboard without visiting the Knowledge base portal first. Simply open your IdP's app portal, locate the Document360 application, and click it to authenticate.
For detailed configuration steps including how to set up the RelayState parameter for direct Knowledge base site redirection, see IdP-initiated sign-in →
Best practices
- Always use your organization's subdomain (not your email address) when logging in, as email-based login is no longer supported for SSO configurations.
- If your organization uses both SSO and non-SSO accounts, make sure you are using the correct login method for each project. SSO and non-SSO logins display different sets of projects.
- If you need access to a Sandbox project as an SSO user, ask your Owner or Admin to apply the same SSO configuration to the Sandbox project and add you as an SSO user there.
FAQ
Why can't I access a project despite being granted access?
You may be added as an SSO user for some projects and a non-SSO user for others. Ensure you are using the correct login credentials for each project. If the issue persists, contact Document360 support.
How can I access the Sandbox project while logged in as an SSO user?
SSO and non-SSO logins are treated as separate permission types and display different sets of projects. To access the Sandbox as an SSO user, ask your Owner or Admin to apply the same SSO configuration to the Sandbox project and add you as an SSO user. Once done, the Sandbox project will appear when you log in with SSO.