Traversing

If a user’s role includes View item permission for a content item, then he/she must be able to find this content item in the Navigator in order to work with it - even if the user does not have View item permission for the parent folders (including the Root folder) of the content item.

Traversing ensures that users will be always able to access all content items for which they have View item permission - even if they do not have permission to access the parent folders.

In this case, the parent folders, including the Root (which would otherwise be hidden from the user) will be visible in the Navigator and the user can traverse through them, but no additional information will be displayed about that parent folder even if the user selects it.

If access to the content item is revoked from the user, these traversed parent folders will automatically disappear too.

Note: Traversing works for all content types, even those without multi-level hierarchies (Roles and users).

Example:

Hierarchy in Navigator:

Folder A

Project A

User A has been granted View item permission for Project A, but does not have any permission for Folder A.

Folder A will be still visible in the Navigator for User A to allow traversing through it, but no additional information will be displayed about Folder A.