Managing Permissions

User access to assets stored in NetX is governed by permissions. Newly created users are unable to access any assets in the system until permissions records are created allowing them to do so. Permissions control which assets users can perform actions on, while user levels control which actions they can perform on said assets.

Administrator-level users are always exempt from any permission controls. 

Permissions entries

Principal

The principal denotes which users will be affected by the permission:

  • Everyone: The permission will affect all users
  • Group: The permission will affect all members of the named group. For more information, see managing groups
  • User: The permission will only affect the named user. Note: user-specific permissions are not recommended.

Note that permissions are cumulative; if a user belongs in two groups, they will be able to access the folders and assets permitted to both groups.

Target

The Target indicates which type of object the principal is permitted to access; either a folder or an individual asset

Folder

If a permission applies to a subfolder (or asset) but not its parent folder, the principal will be allowed to navigate to the subfolder but its parent folders will appear empty. Any sibling folders will be hidden.

Once a Folder target is selected, an input line will appear. Type the name of the folder you want to give your principal explicit access to. Two things to note regarding folder permissions:

  • Top level: If the target folder is set to Top Level Folder (/), they will have access to all folders and assets.
  • Recursive: If the Recursive box is checked, the principal will have access to all subfolders and assets contained inside the target folder. If Recursive is not checked, the principal will only see assets within the target folder itself. 

Asset

Once an Asset target is selected, an input line will appear. Type the file name of the asset and select it from the drop-down. A principal who is granted access to a single asset can only access that specific asset within a folder. Note: asset-specific permissions are not recommended.

Creating a permission

  1. Click the Systems button found along the lefthand navigation sidebar.
  2. Click the Permissions tab.
  3. Choose a Principal.
  4. Choose a Target
  5. Click Save.

Editing a permission

  1. Click the Systems button found along the lefthand navigation sidebar.
  2. Click the Permissions tab.
  3. Use the action menu icon for the specific permission and choose Edit permission.
  4. Modify the Principal and/or Target for the permission.

Deleting a permission

  1. Use the Systems button found along the lefthand navigation sidebar to access the systems area.
  2. Navigate to the Permissions tab.
  3. Use the action menu icon for the specific permission and choose Delete permission.
  4. Click Delete on the subsequent confirmation dialogue to delete the permission.

Tips and tricks

  1. Apply permissions to folders and groups.
    Avoid creating individual user or asset permissions; they are hard to manage and can slow the system down.
  2. Using recursive folder permissions keeps administration simple.
    Isolating restricted content reduces the complexity of your permissions.
  3. Be aware of reindexing.
    Creating or changing a permission will trigger a site-wide reindex and could temporarily impact performance.
Was this article helpful?
0 out of 0 found this helpful