Site access

Plans supporting access to public, Private, and Mixed Knowledge base site

Site access refers to the visibility setting in your Document360 project that determines who can view the content of your Knowledge base site.

To manage site access, from the knowledge base portal, navigate to () > Users & security > Site access.

The three available site access modes are

• Public

• Private

• Mixed

Public access

A public access Knowledge base site is accessible by everyone on the web. The published content of the Knowledge base can be accessed with direct links or via search engines on the web browser. No login is required.

Examples include:

• customer support knowledge base site

• product help center site

• self-service portal

• public API documentation

• user guides and manuals

Private access

A private knowledge base means that the content is kept secure and private, only accessible to specific people with a Reader account or Team account. It is not open to the public.

Examples include:

• internal IT support KB site

• HR policies and procedures

• company-wide knowledge sharing

• internal API documentation

• proprietary software documentation

When a knowledge base is set to Private, readers must sign in with their credentials to view the content.

Mixed access

A Mixed access knowledge base is a hybrid site access setting that allows parts of the knowledge base to be public and parts of the Knowledge base to be private access only for the reader accounts with login credentials.

Examples include:

• public support articles with private internal docs

• customer-facing help center with internal HR KB

• public API with internal developer notes

• customer-facing compliance with internal audit trails

• public developer resources with private development guides

Managing site access settings

To view and manage the site access settings in your project,

1. From the Knowledge base portal, navigate to () > Users & security > Site access.

   Your project's site access will be marked selected in this section.

   You can switch between the three access settings.

2. Click the desired site access option to switch your project's visibility setting.

   An Update visibility confirmation prompt will be displayed.

3. Enter your project subdomain in the pop-up. For example: document360-demo

   

4. Once done, click the Yes button.

   The site visibility for the project will be changed.

   NOTE

   When switching from Mixedto Private or from Private to Mixed, you might want to reconsider the previously assigned access permissions.

Updating site access

For example, if you wish to change the site access of your knowledge base from Private to Mixed,

1. Log in to the Knowledge base portal and select your project.

2. In your project, navigate to > Users & security > Site access.

3. Under the Knowledge base site visibility for project section, select the () Mixedradio button.

4. In the Update site access popup, enter your project subdomain in the given field, and click Yes.

You have now successfully updated the site access of your project from Private to Mixed.

Changing site access settings at the project level

To change site access settings at the project level,

1. Navigate to () >  Users & security > Site access in the Knowledge base portal.

2. The project name would be visible at the top, and below that, a tree view of the versions and languages will be available.

3. Expand the project name and you can change the workspace version and the language of the project.

   You can manage the content access of Readers or Reader group(s) with the list of the reader(s) and reader available with information like profile image, name, email, content access, and reader group.

4. To search for any specific reader or reader group, use the search bar along with the Filter () option.

   You can filter content access based on Project, Workspace, and Language.

5. To clear the existing filters, click the Clear all option.

6. To remove the project-level site access of any reader or reader group from the list, click the Remove () icon available to the right when you hover over it.

7. To deny access from a reader or a reader group, click the Deny () icon.

   NOTE

   When a project-level setting and version/language level access are added for the reader(s) or reader group(s), then the version/language level content access would take precedence over any project-level site access.

Assign workspace access

To assign workspace access to any reader,

1. Click the Assign workspace access button from the list of Readers and Readers group.

2. Once selected, click the Apply button.

   The selected reader or reader group will now have the assigned access permissions.

For more information on adding readers to a project and activating emails to notify them, read the article on Managing readers.

SSO login issue: HTTP 500 error

Error: This page isn’t working - identity.document360.io is currently unable to handle this request - HTTP 500 ERROR

Steps to resolve:

1. Check if the issue is affecting all users associated with the project’s SSO Identity Provider.

2. If the issue is isolated to a specific user, it may be related to browser or network settings.

3. Try logging in using an incognito/private browsing panel.

4. Switch to a different internet connection and attempt the login.

5. Use a different device to log in and see if the issue persists.

6. Als het probleem zich blijft voordoen na het volgen van deze stappen, neem dan contact op met het Document360-ondersteuningsteam voor verdere hulp: Neem contact op met Document360 Support

   Provide the following details:

   • SSO configuration details for the project and the associated Identity Provider.

   • A generated product log file. For instructions, read the article on Generating a HAR File.

   • A screen recording that demonstrates the issue in detail.

JWT login issue: Unauthorized access

Error: Sorry, you're not authorized to access this documentation. Invalid authentication code.

You might encounter this error when logging in to the Knowledge base site using the JWT configured for reader accounts in the project due to unauthorized access.

Steps to resolve:

1. Check if the issue is widespread or isolated: Determine whether the problem affects all readers in the project or is specific to readers from a particular region or network.

   For issues affecting a specific user:

   1. Ask the user to log in using an incognito/private browsing panel.

   2. Try accessing the site using a different internet connection.

   3. Attempt logging in from another device to identify if the issue is device-specific.

2. Als het probleem zich blijft voordoen na het volgen van deze stappen, neem dan contact op met het Document360-ondersteuningsteam voor verdere hulp: Neem contact op met Document360 Support

   Provide the following details:

   • A generated product log file. For instructions, read the article on Generating a HAR File.

   • A screen recording that demonstrates the issue in detail.