Documentation Index

Fetch the complete documentation index at: https://docs.document360.com/llms.txt

Use this file to discover all available pages before exploring further.

Convert to SSO account

Prev Next

Converting a Document360 account to an SSO account lets users and readers authenticate using their Identity Provider (IdP) credentials instead of a separate Document360 password. The conversion preserves all existing roles and access permissions, so nothing needs to be reconfigured after the switch. You can convert individual accounts or multiple accounts at once, for both users and readers.


Before you begin

  • Your project must have SSO configured using SAML or OpenID Connect. Conversion is not available for JWT-configured projects.
  • You must have the Owner or Admin project role, or a custom role with the Manage users permission.
  • A user cannot convert their own account. The conversion must be performed by another Owner, Admin, or user with the Manage users permission.

Choose what to convert

Convert users

Convert existing standard user accounts in your project to SSO accounts.

Go to steps →

Convert readers

Convert existing standard reader accounts on your knowledge base site to SSO accounts.

Go to steps →

Convert users to SSO accounts

  1. Navigate to Settings () in the left navigation bar of the Knowledge base portal.
  2. In the left navigation pane, go to Users & permissions > Users.
  3. Select the checkbox next to the users you want to convert.
  4. Click the Convert to SSO account option above the user list.
User management interface displaying account statuses and options for user roles.

An Account convert confirmation popup appears.

  1. Select the confirmation checkbox and click Yes.
User account conversion prompt for Vitsy Agent to SSO account with options.
NOTE

Keep the following in mind when converting users:

  • All contributions made by the user before conversion are retained, but they will appear as Anonymous after conversion.
  • A user cannot convert their own account. Another Owner or Admin must perform the conversion.
  • If you convert an Owner account to SSO, both the original Document360 account and the new SSO account will remain active. This means the same person will have two separate accounts.
  • Users must be added and configured as SSO accounts in Document360 with the appropriate access permissions for successful login.

Convert readers to SSO accounts

  1. Navigate to Settings () in the left navigation bar of the Knowledge base portal.
  2. In the left navigation pane, go to Knowledge base site > Users & permissions > Readers & groups > Readers.
  3. Select the checkbox next to the readers you want to convert.
  4. Click the Convert to SSO account option above the reader list.
User management interface showing reader accounts and options for SSO conversion.

An Account convert confirmation popup appears.

  1. Select the confirmation checkbox and click Proceed.
User account conversion prompt for SSO configuration in Document360 interface.
NOTE

An SSO account cannot be converted back to a standard Document360 account. If you need to revert a conversion, you must delete the SSO account and recreate the standard account manually, replicating the original roles and access.


Best practices

  • Before converting accounts in bulk, do a small test conversion with one or two users and confirm they can log in successfully via SSO before proceeding with the rest.
  • Avoid converting Owner accounts to SSO unless necessary, since the conversion results in two active accounts for the same person. Manage this carefully to avoid access confusion.
  • Keep a record of the roles and access settings for accounts you plan to convert, in case you ever need to recreate a standard account manually.

FAQ

Who can perform the conversion of a Document360 account to an SSO account?

Owners and Admins can perform this conversion. Users with the Manage users permission can also perform this action.

Can I perform user-type conversion in JWT-configured projects?

No. User-type conversion is only available in projects configured with SAML or OpenID Connect. It is not supported in JWT-configured projects.

I accidentally converted users or readers to SSO accounts. How can I fix this?

There is no direct way to reverse a conversion. To fix this, delete the SSO account and recreate the standard Document360 account manually. Make sure to replicate the original roles and access permissions exactly.

How can I access both the Production and Sandbox projects using SSO?

If your Production project has SSO configured but your Sandbox project does not, you will not be able to access both using the same SSO credentials. To resolve this:

  1. Set up SSO in the Sandbox project using the same Identity Provider configured in the Production project.
  2. During setup, select Configure an existing connection to reuse the same SSO configuration.
  3. Add your SSO users to the Sandbox project with the required roles and permissions.
  4. Once complete, both the Production and Sandbox project tiles will appear on your dashboard when you log in with SSO.