Primary access keys and sub-access keys

You must use a primary access key to share transfer access outside your AoC organization, such as with a vendor or other collaborator, or with a downstream on-prem application like Aspera Faspex, Shares, or Console. Use a sub-access key to share transfer access inside your AoC org, such as when delegating access and management tasks to a workspace manager.

Primary access keys

Use a primary access key to give a user or application outside Aspera on Cloud transfer credentials to access the content assets on that node.

An Aspera on Cloud superadmin (an administrator who knows the Aspera transfer user name and password) can create a primary access key in two ways:

Sub-access keys

Use a sub-access key to delegate certain administrative tasks and contextual content access to another AoC admin or to a workspace manager without having to distribute the primary access key. You can create a sub-access key only on a sub-directory of another access key.

Important: To maintain tenant privacy and content separation, do not use a sub-access key outside the context of the Aspera on Cloud organization.
An Aspera on Cloud administrator can use the primary access key to create either of two sub-access key types, using the Aspera on Cloud application.
  • A client sub-access key (also called a workspace access key) gives an admin or workspace manager contextual access and management rights within the root folder of a given workspace on the node.
  • A folder sub-access key gives an admin or workspace manager access and management rights in a folder in cloud storage or in an administratively shared folder.

    Note that a folder sub-access key is a different access credential than the sharing permissions set on a shared folder. Access through a folder sub-access key is full access to folder contents;such access is not restricted to the actions allowed through sharing permissions.