Accessible Content

General

A user’s accessible content defines the set of folders that the user can access. These are the set of folders that a user will see in the system. Accessible content limitations are enforced in the Repository, in search, and via the API. Accessible content is related to Data Groups.

Granularity

Accessible content for any user can be configured to include all folders in the Repository or restricted to an arbitrary set of folders in the Repository. A user may also be denied access to the Repository all together. To edit a user’s accessible content, see Modifying Accessible Content.

Effect on Repository

When entering the Repository, restricted users will only see folders allowed by their accessible content. Any folder that has been excluded from a user’s accessible content will simply not appear in the Repository. As a result, the Repository may look different for different users, especially at the top most level because it will only show the highest-level ancestor for the folder trees each user can access.

Special Considerations

Though it’s possible to disallow access to the Repository for any user, there are side effects that make this not suitable for administrators in particular. Users that have NULL accessible content (i.e. do not have access to any folders) will experience some limitations, regardless of their permission level. For instance, the following capabilities will not be available for these users:

  • Cannot access the Data Groups tab in Settings
  • Cannot access the Data Group dropdown during user creation
  • Will not see the Accessible Content column in the users table
  • Cannot Edit Accessible Content menu option in the users table