To submit a question or request advice, select the Advisor mode.
To initiate an operational task if your account is entitled, select the Work mode.
Enter the prompt stating the specific requirement.
Evaluate the agent response or the proposed plan of action.
(Work mode only) Provide approval because the agent executes actions only after explicit human confirmation.
The system authenticates your user account through the active Acquia identity. Advisor mode does not require an onboarding wizard, API keys, and module installation to begin operation.
Accessing Acquia AI
Getting started with Acquia AI
Logging into and operating Acquia AI
To access the Acquia AI interface, follow these steps:
To submit a question or request advice, select the Advisor mode.
To initiate an operational task if your account is entitled, select the Work mode.
Enter the prompt stating the specific requirement.
Evaluate the agent response or the proposed plan of action.
(Work mode only) Provide approval because the agent executes actions only after explicit human confirmation.
The system authenticates your user account through the active Acquia identity. Advisor mode does not require an onboarding wizard, API keys, and module installation to begin operation.
Accessing Acquia AI
Access to Acquia AI depends on two factors: account eligibility and an access grant from an organization administrator.
Account eligibility
Acquia enables Acquia AI for an account with one of these entitlements:
Acquia Source CMS
Acquia Cloud Platform, including Cloud Trial and Multi Experience Operations
A new Acquia Web Governance account
A new Acquia DAM account
Note
Existing Acquia Web Governance accounts, existing Acquia DAM accounts, and Acquia Site Factory do not qualify. Acquia plans to extend Acquia AI to those products in 2027.
Acquia enables accounts in phases. Every user who holds the administrator role on Acquia Cloud receives an email after Acquia enables the subscription for that organization.
Access grant structure
Acquia AI maintains a dedicated access list, separate from roles or permissions in Acquia Cloud Platform, Acquia Source CMS, or other Acquia products. Team membership and role-based permissions do not affect Acquia AI access.
Access is granted to an Acquia AI project. In this release, every organization holds one project, named Default Project, so a grant to that project provides access to Acquia AI. The grant covers both operational modes: users must hold access to submit queries in Advisor mode and to delegate tasks in Work mode.
Access rules include:
Explicit administrator grants: Users do not hold access until an organization administrator grants it. Before access is granted, only organization administrators can open Acquia AI. Administrators select which organization members receive access.
Administrator authority: Only an organization administrator can grant access. Anyone who holds an administrator role in the organization can perform this action. Organizations typically hold one owner role and several administrator roles. In this release, administrators cannot pass this capability to other roles.
Individual user grants: Access is granted one person at a time. Procedures to grant access to an entire role or team are unavailable in this release, so administrators must grant access to each person individually.
Access grants take effect immediately. A grant to an existing organization member is not an invitation: the system sends no messages, and the user accepts no prompts. Removal of a person from every project revokes Acquia AI access immediately and terminates the use of both operational modes.
Grant access to a user
Prerequisites
Ensure that the setup meets the following requirements:
Hold an administrator role in the Acquia organization. Both the organization owner role and the administrator role qualify.
Hold an eligible account entitlement.
Procedure
To grant user access:
Sign in at source.acquia.com with an account that holds the administrator role in the organization.
In the left navigation, under AI, select Users.
Locate the person in the organization list. This list displays all members of the Cloud organization. Users must belong to the organization to appear in the list.
Select Manage projects, then add the person to Default Project.
Repeat these steps for each person who requires access.
If Acquia AI opens, an organization administrator has granted access, and both Advisor mode and Work mode are available.
If Acquia AI does not open, either the account is not enabled for Acquia AI or an organization administrator has not granted access. Contact an organization administrator. Users who hold the administrator role maintain automatic access.
Scope of access grants
Access to Acquia AI requires a single grant that covers both operational modes. Users need this grant to ask questions in Advisor mode and to delegate work in Work mode. No features in Acquia AI are reachable without this grant. Advisor mode consumes no AI credits, but access remains restricted. Organizations that must prevent AI access entirely do so by withholding the grant.
AI credit availability functions independently of access grants. Work mode consumes AI credits, and credit limits apply to the subscription rather than individual users. When credit balances reach zero, new Work mode tasks wait for credit additions or renewals. Advisor mode continues to function. For additional details, visit AI credits and usage.
Differences between the two modes involve agent reach and credit consumption rather than access authorization. For additional details, visit Modes in Acquia AI.
Assign the agent to an application and a site
A permission grant to a user provides the agent with no target to act on. The agent operates through a separate identity called the Agents Team. An organization administrator must add each application and site that the agent must reach to the Agents Team, in the same manner as human team members.
To assign a Cloud Platform application:
In Acquia AI, navigate to Permissions, then select Cloud Platform.
Select Agents Team.
Assign one or more applications to the team, then save.
Optional: Select Edit roles next to the agent name to change Agents Team role permissions or add another role.
By default, the Agents Team role holds a starter permission set. An administrator can adjust permissions per environment to allow actions on a non-production environment while withholding permissions on production.
To assign a Source CMS site:
In Acquia AI, navigate to Permissions, then select Source CMS.
Select Agents Team.
Assign one or more sites to the team, then save.
Source CMS provides no permission control for the agent. The agent holds a fixed member role, which limits administrator configuration to site selection.
Acquia DAM follows a separate path. A DAM administrator configures and scopes the agent directly inside Acquia DAM Admin Tools instead of Acquia AI. Once configured, the agent reaches only the scope granted by that administrator. For additional details, visit Find assets in Acquia DAM.
Permanent boundaries
A grant to the Agents Team does not extend agent capabilities beyond current release boundaries. Even on assigned applications, the agent does not modify application code or infrastructure configurations. The agent analyzes logs only for diagnosis tasks and returns findings rather than raw log entries. For additional details, refer to Governance and control management.
Remove access
To remove access, remove the application or site from the Agents Team assignment. The agent loses access to that resource immediately. On Acquia DAM, a DAM administrator removes the agent role inside DAM Admin Tools.
Projects, agents, and context groups
Work in Acquia AI occurs inside a project workspace.
Project: The workspace for a body of work. In this release, an organization holds one project.
Project agent: The Agents Team identity that performs tasks in Work mode. The project agent holds no settings apart from team assignment and assigned roles.
Context group: A named set of reference files and text that an administrator creates once and applies to a project. Brand guidelines, tone of voice documents, and component inventories serve as examples.
To add context to a project:
Access the Context tab inside the project.
Select Create context group.
Upload the reference file or text.
Save the group. The agent references this material during tasks.
To apply an existing context group:
Access the Context tab inside the project.
Under Context groups, select Apply a group.
Select the group for agent use.
Share a project
Users can share a project with another user in the organization. Invited users must belong to the organization and hold Acquia AI access.
When a project is shared, every member can use the project agent and review the conversation history of all other members in that project.
Access to Acquia AI depends on two factors: account eligibility and an access grant from an organization administrator.
Account eligibility
Acquia enables Acquia AI for an account with one of these entitlements:
Acquia Source CMS
Acquia Cloud Platform, including Cloud Trial and Multi Experience Operations
A new Acquia Web Governance account
A new Acquia DAM account
Note
Existing Acquia Web Governance accounts, existing Acquia DAM accounts, and Acquia Site Factory do not qualify. Acquia plans to extend Acquia AI to those products in 2027.
Acquia enables accounts in phases. Every user who holds the administrator role on Acquia Cloud receives an email after Acquia enables the subscription for that organization.
Access grant structure
Acquia AI maintains a dedicated access list, separate from roles or permissions in Acquia Cloud Platform, Acquia Source CMS, or other Acquia products. Team membership and role-based permissions do not affect Acquia AI access.
Access is granted to an Acquia AI project. In this release, every organization holds one project, named Default Project, so a grant to that project provides access to Acquia AI. The grant covers both operational modes: users must hold access to submit queries in Advisor mode and to delegate tasks in Work mode.
Access rules include:
Explicit administrator grants: Users do not hold access until an organization administrator grants it. Before access is granted, only organization administrators can open Acquia AI. Administrators select which organization members receive access.
Administrator authority: Only an organization administrator can grant access. Anyone who holds an administrator role in the organization can perform this action. Organizations typically hold one owner role and several administrator roles. In this release, administrators cannot pass this capability to other roles.
Individual user grants: Access is granted one person at a time. Procedures to grant access to an entire role or team are unavailable in this release, so administrators must grant access to each person individually.
User labels: Organization administrators hold access by default and appear as Acquia AI Admin. Added members appear as Member. Both labels use Acquia AI identically, the label indicates only whether a user holds the organization administrator role.
Access grants take effect immediately. A grant to an existing organization member is not an invitation: the system sends no messages, and the user accepts no prompts. Removal of a person from every project revokes Acquia AI access immediately and terminates the use of both operational modes.
Grant access to a user
Prerequisites
Ensure that the setup meets the following requirements:
Hold an administrator role in the Acquia organization. Both the organization owner role and the administrator role qualify.
Hold an eligible account entitlement.
Procedure
To grant user access:
Sign in at source.acquia.com with an account that holds the administrator role in the organization.
In the left navigation, under AI, select Users.
Locate the person in the organization list. This list displays all members of the Cloud organization. Users must belong to the organization to appear in the list.
Select Manage projects, then add the person to Default Project.
Repeat these steps for each person who requires access.
If Acquia AI opens, an organization administrator has granted access, and both Advisor mode and Work mode are available.
If Acquia AI does not open, either the account is not enabled for Acquia AI or an organization administrator has not granted access. Contact an organization administrator. Users who hold the administrator role maintain automatic access.
Scope of access grants
Access to Acquia AI requires a single grant that covers both operational modes. Users need this grant to ask questions in Advisor mode and to delegate work in Work mode. No features in Acquia AI are reachable without this grant. Advisor mode consumes no AI credits, but access remains restricted. Organizations that must prevent AI access entirely do so by withholding the grant.
AI credit availability functions independently of access grants. Work mode consumes AI credits, and credit limits apply to the subscription rather than individual users. When credit balances reach zero, new Work mode tasks wait for credit additions or renewals. Advisor mode continues to function. For additional details, visit AI credits and usage.
Differences between the two modes involve agent reach and credit consumption rather than access authorization. For additional details, visit Modes in Acquia AI.
Assign the agent to an application and a site
A permission grant to a user provides the agent with no target to act on. The agent operates through a separate identity called the Agents Team. An organization administrator must add each application and site that the agent must reach to the Agents Team, in the same manner as human team members.
To assign a Cloud Platform application:
In Acquia AI, navigate to Permissions, then select Cloud Platform.
Select Agents Team.
Assign one or more applications to the team, then save.
Optional: Select Edit roles next to the agent name to change Agents Team role permissions or add another role.
By default, the Agents Team role holds a starter permission set. An administrator can adjust permissions per environment to allow actions on a non-production environment while withholding permissions on production.
To assign a Source CMS site:
In Acquia AI, navigate to Permissions, then select Source CMS.
Select Agents Team.
Assign one or more sites to the team, then save.
Source CMS provides no permission control for the agent. The agent holds a fixed member role, which limits administrator configuration to site selection.
Acquia DAM follows a separate path. A DAM administrator configures and scopes the agent directly inside Acquia DAM Admin Tools instead of Acquia AI. Once configured, the agent reaches only the scope granted by that administrator. For additional details, visit Find assets in Acquia DAM.
Permanent boundaries
A grant to the Agents Team does not extend agent capabilities beyond current release boundaries. Even on assigned applications, the agent does not modify application code or infrastructure configurations. The agent analyzes logs only for diagnosis tasks and returns findings rather than raw log entries. For additional details, refer to Governance and control management.
Remove access
To remove access, remove the application or site from the Agents Team assignment. The agent loses access to that resource immediately. On Acquia DAM, a DAM administrator removes the agent role inside DAM Admin Tools.
Projects, agents, and context groups
Work in Acquia AI occurs inside a project workspace.
Project: The workspace for a body of work. In this release, an organization holds one project.
Project agent: The Agents Team identity that performs tasks in Work mode. The project agent holds no settings apart from team assignment and assigned roles.
Context group: A named set of reference files and text that an administrator creates once and applies to a project. Brand guidelines, tone of voice documents, and component inventories serve as examples.
To add context to a project:
Access the Context tab inside the project.
Select Create context group.
Upload the reference file or text.
Save the group. The agent references this material during tasks.
To apply an existing context group:
Access the Context tab inside the project.
Under Context groups, select Apply a group.
Select the group for agent use.
Share a project
Users can share a project with another user in the organization. Invited users must belong to the organization and hold Acquia AI access.
When a project is shared, every member can use the project agent and review the conversation history of all other members in that project.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
User labels: Organization administrators hold access by default and appear as Acquia AI Admin. Added members appear as Member. Both labels use Acquia AI identically, the label indicates only whether a user holds the organization administrator role.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Source