A permission grants a user the ability to perform specific operations in an Acquia subscription. Permissions are grouped into roles. Roles are then assigned to team members. All the team members who have the same roles have the same permissions.
Acquia defines over 40 separate permissions, grouped into these categories:
- Server administration
- SSH keys
- Help requests
The available permissions are listed in the List of permissions table. You can also view all the available permissions by opening the Manage roles page and edit a role, as described in Working with roles and permissions: Editing a role.
Many permissions enable you to distinguish between team members who can work on a site's production environment and team members who can only work on the non-production (Dev and Stage) environments. For example, the Senior Developer role includes the permissions to pull and deploy code in production and non-production environments, while the Developer role grants permission to to pull and deploy code only in non-production environments. Since Acquia Cloud Free sites do not have production environments, those permissions do not apply to those sites.
Permissions in Acquia subscriptions do not control actions users take on your Drupal site, such as:
- Creating content
- Enabling and configuring Drupal modules
- Adding or removing Drupal users
Use the Drupal permissions administration to control access to Drupal functions.
|Permission||Acquia Cloud Enterprise||Acquia Cloud Professional||Acquia Cloud Free||Acquia subscription only|
|Add or remove a user of a team. This includes the ability to assign a user's role, and therefore allows a user with this permission give themselves any role, including Team Lead.|
|Access the Cloud API.
Using the Cloud API, authorized users can bypass all other permissions, using command-line tools.
|Activate an Acquia subscription add-on.|
|Modify cron tasks for non-production environments.|
|Modify cron tasks for the production environment.|
|Add a database.|
|Remove a database.|
|View database connection details (username, password, or hostname).|
|Download database backups for non-production environments.|
|Download database backups for the production environment.|
|Create database backups for non-production environments.|
|Create database backups for the production environment.|
|Restore database backups for non-production environments.|
|Restore database backups for the production environment.|
|Add or remove domains to non-production environments.|
|Add or remove domains to the production environment.|
|Add or remove SSL Certificates.|
|Manage Insight alerts.
Users with this permission can set Insight alerts to 'Ignore' and can also change Drupal settings using the Fix-it-now feature.
|Manage Insight site groups.|
|Download logs for non-production environments.|
|Download logs for the production environment.|
|Increase the search index limit on a subscription.|
|Edit the search schema on a subscription.|
|Add SSH key to git repository.|
|Add SSH key to non-production environments.|
|Add SSH key to production environment.|
|Create a help request.|
|View and edit any help requests for a subscription.|
|Include as a collaborator on all help requests by default.|
|Pull and deploy code, files, or databases to non-production environments.
Also grants the ability to enable or disable live development.
|Deploy code, files, or databases to the production environment.|
|Pull files or databases from the production environment.|
|Move files to non-production environments.|
|Move files to the production environment.|
|Move files from production environments.|
|Move files from non-production environments.|
|Clear Varnish cache for non-production environments.|
|Clear Varnish cache for the production environment.|
|Configure production environment.|
|Configure non-production environments.|