Access management structure in DoubleCloud Visualization

In DoubleCloud Visualization, you can manage access on collections and workbooks level with user permissions.

The following diagram shows the hierarchy of user role levels in DoubleCloud Visualization:

There are two role levels in Visualization:

  • Inherited - a user role(s) applied at a higher structural level.

    For example, the user role for the collection will be automatically inherited for all the workbooks inside this collection.

  • Direct - a user role applied directly to the user of a selected entity.

    For example, you can assign a user with the viewer role in a collection as an editor for a specific workbook within this collection.


In DoubleCloud Visualization, you can only elevate the user's role compared to their project role.

For example:

  • You can assign an editor or viewer role to a user with the admin project role, but they'll always retain their administrative access and privileges.

  • At the same time, a user with the viewer project role can be elevated to editor or admin within a collection or workbook.

There are three user permissions in DoubleCloud Visualization:

  • Viewer: this user role can view workbooks, datasets, charts and dashboards.

    This user role doesn't allow to copy datasets because they contain RLS settings.

  • Editor: this user can edit collections, workbooks, workbooks, datasets, charts and dashboards.

  • Admin: this user can create, modify and delete entities within workbooks or collections. This user can also manage access to collection and workbooks.

See also