A permission grants a user the ability to perform specific operations in an Acquia Cloud organization or application. 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:
- SSH keys
- Server administration
The available permissions are listed in the List of permissions table. You can also view all the available permissions by opening the Roles page for an organization and viewing a role, as described in Working with roles and permissions: Viewing a role's permissions.
Many permissions enable you to distinguish between team members who can work on an application'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 pull and deploy code only in non-production environments. Since Acquia Cloud Free applications do not have production environments, those permissions do not apply to those applications.
Permissions in Acquia Cloud do not control actions users take on your Drupal website, 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.
|Category||Permission||Acquia Cloud Enterprise||Acquia Cloud Professional||Acquia Cloud Free|
|Administration||Access the Cloud API
Using the Cloud API, authorized users can bypass all other permissions by using command-line tools.
|Activate an Acquia subscription add-on|
|Add or remove a user of a team
This includes the ability to assign a user's role, allowing a user with this permission give themselves any role, including Team Lead.
|Edit Remote administration|
|View Remote administration|
|Cron||Modify cron tasks for non-production environments|
|Modify cron tasks for the production environment|
|Databases||Add a database|
|Create database backups for non-production environments|
|Create database backups for the production environment|
|Download database backups for non-production environments|
|Download database backups for the production environment|
|Remove a database|
|Restore database backups for non-production environments|
|Restore database backups for the production environment|
|View database connection details (username, password, or hostname)|
|Domains||Add or remove SSL certificates for the non-production environments|
|Add or remove SSL certificates for the production environments|
|Add or remove domains for non-production environments|
|Add or remove domains for the production environment|
|Insight||Block Insight sites
Users with this permission can prevent applications from submitting data to Acquia Insight.
|Manage Insight alerts
Users with this permission can set Insight alerts to Ignore.
|Revoke Insight environment|
|Logs||Download logs for non-production environments|
|Download logs for the production environment|
|SSH keys||Add SSH key to git repository|
|Add SSH key to non-production environments|
|Add SSH key to the production environment|
|Manage SSH keys|
|Search||Edit the search schema on a subscription|
|Increase the search index limit on a subscription|
|Server administration||Configure server|
|Support||Create a support ticket|
|Include as a collaborator on all tickets by default|
|View and edit any support tickets for a subscription|
|Workflow||Add an environment|
|Clear Varnish cache for non-production environments|
|Clear Varnish cache for the production environment|
|Configure non-production environments|
|Configure production environment|
|Delete an environment|
|Deploy code, files, or databases to the production environment|
|Move files from non-production environments|
|Move files from production environments|
|Move files to non-production environments|
|Move files to the production environment|
|Pull and deploy code, files, or databases to non-production environments
Also grants the ability to enable or disable live development.
|Pull files or databases from the production environment|