Skip to main content
Version: 2.8

Setting ACL on Content Level in ADx Explorer

Default Access to Contents

The default access permission to any content is Deny for all users except for the content's owner. To make a content available to other users, users must be granted access by one of the following ways:

  • An administrator can give certain users access by setting ACL rules on the repository level.

  • The content owner can give others access by setting ACL rules on the content itself.

Public Contents

Public contents are contents that fulfill all of the following:

  • They don't have an owner
  • They don't have any ACL set up.

Granting Access Only to Certain Users for a Content

To grant access to certain users who are not owners of a content:

  1. Select the content.
  2. Go to More Actions > Access Control > Grant Access.
  3. Select an Operation that you want to grant these users such as Read or Download.
  4. In Role, click the dropdown button to select a user, group, or role. For example, To grant a user called John, select $user-John.

Blocking Certain Users from Accessing Contents

To grant access to certain users who are not owners of a content:

  1. Select the content.
  2. Go to More Actions > Access Control > Deny Access.
  3. Select an Operation that you want to deny to these users such as Read or Download.
  4. In Role, click the dropdown button to select a user, group, or role. For example, To deny access to a user called John, select $user-John.

Who Can Access Contents in CMIS and Documentum Repositories

CMIS and Documentum repository contents can be accessed in one of the following cases:

  • The user logged in to ADx has the same username and password used to connect to the CMIS or Documentum system. You can find these credentials in the details of a CMIS or Documentum repository.
  • If not, a user must be given access to CMIS or Documentum repositories explicitly on the repository level by an administrator. For more information, see Setting Repository ACL.