Document360 enables you to allocate roles, each with a distinct permission set, defining their access, editing, and configuration rights within the project.

To simplify this process, Document360 has categorized the roles into Portal and Content roles.

We have made significant changes in this space to ensure a smoother and more tailored experience when assigning permissions to different user groups.

Consolidated permissions

We have consolidated all the permissions as view, update, delete and publish.

  • View - As the name suggests, users assigned this permission can only access the designated feature or function.

  • Update - Users assigned with this permission can perform update actions such as creating, editing, hiding/unhiding, and reordering items in the knowledge base.

  • Delete - Users can delete the articles, categories, and while assigned with this permission respective view, update permissions will be auto-enabled, which reduces manual intervention to enable it.

  • Publish - Users can publish articles and customize changes in the Knowledge base site.

To achieve this, we have put together functionalities in a familiar place.

Below is an example of one of the fundamental changes Document360 has executed in the new implementation and renamed to align with existing functions.

Content Roles - Old vs 2.0 configuration


Content role changes



Portal role changes


The Custom roles created by users in Document360 1.0 will be available in the newly revamped 2.0 portal. However, the roles will be updated with an additional one or more permissions. We suggest you revisit the custom role permissions created and assigned to the respective user groups.

Contributors with Editor permissions only will still be able to publish the content reflected in the Knowledge base site.