Permission Overview
Permissions allow users certain type of access to records and containers. The specifics permissions are detailed in this section.
Record Classes
Accounts with the User security role, will need to be given specific permissions on a Record Class for access to any records that that belong to it.
| Permission | Comment |
|---|---|
| View Record Details | The ability to view details about the records including properties and lifecycle details. |
| Declare | Declare as a record. Also allows a record to be marked superseded or obsolete. |
See the topic on Record Class Permission for more information.
Physical Records
Accounts with the Physical User role wll need to be given specific permissions in order to access container and assets.
Child Containers
A Physical User cannot be given create/edit/delete permission to root containers regardless of the permissions that are set and must be assigned specific access to child containers. In the following table, the permissions are shown from least privileged to most privileged, meaning View is the least, and Delete is the most.
| Permission | Comment |
|---|---|
| View | View a container. Without View, a user won't be able to see or search for any assets. This is the lowest privileged assignment and does not adopt any other permissions. |
| Create | Create a new child container under the given container. |
| Edit | Edit the container all the properties for a container, apply custom metadata, as well as the ability to drag/drop and cut/paste. |
| Edit Permission | Edit the permission of a container. |
| Delete | Delete the container. This is the highest privileged assignment and adopts all the other permission with it. |
Assets
In the following table, the permissions are shown from least privileged to most privileged, meaning View is the least, and Delete is the most. Some of the permission may also require permissions on the container itself in order to get the expected results.
| Permission | Comment |
|---|---|
| View | View the properties, metadata, and record details on assets in the container. This is the lowest privileged assignment and does not adopt any other permissions. |
| Create | Create a new asset in the container. Edit must also be given on the container. |
| Edit | Edit the metadata on assets in the container. Edit must also be given on the container. |
| Delete | Delete the asset. Edit must also be given on the container. |
In addition to the permissions above, the following permissions require specific assignments in order for them to work.
| Permission | Comment |
|---|---|
| Copy | Copy the asset to another location. The user must have Edit access to the target location for Copy/Paste or Drag/Drop to work. |
| Move | Move the asset to a new location. The user must have Edit access on both the source and target location for Copy/Paste or Drag/Drop to work. In addition, users are only allowed to move assets to the same Node type. |
Locations
Physical users can only View locations, and cannot be assigned permissions to create, edit, or delete locations.
Barcode
A Physical User does not have the ability to create, edit, or delete barcode schemas. They will have the ability to enter barcodes if they have at least Edit permissions on both the container and the asset. Once a barcode is saved on an asset, a user can no longer edit them.