Acquia AI maintains a strict boundary. This page states what the agent does not do and explains the function of the agent role and permission set. For a full account of data practices, visit Data handling, privacy, and security.

Governance principles

Governance rests on three core principles:

• Bounded capability set: The agent does not modify application code or infrastructure configurations.

• Scoped agent role: The agent holds a dedicated Agents Team role, separate from user roles, and never inherits permissions from the requesting user. On Cloud Platform, an administrator configures exact permissions for that role per environment to permit an action on one environment and withhold it on another.

• Two-stage approval: The agent proposes a plan and takes no action without human approval. Publication requires a second, separate approval.

What Acquia AI does not do

Actions

• Performs no actions without approval.

• Does not modify application code or code repositories.

• Does not modify infrastructure configurations, such as cache clears, domain name record changes, or certificate installations.

• Takes no corrective action on a diagnosis. The agent states where evidence points and recommends next steps for accessibility fixes. The code owner must apply the fix.

• Does not block publication because of a low governance score.

Oversight and escalation

• Does not perform continuous monitoring. The agent responds to requests and does not observe sites or environments independently.

• Does not search logs independently. The agent reads logs only for user-delegated diagnosis tasks within a specified environment and time window.

• Cannot submit a support case.

• Does not resolve live outages or critical issues. Contact Acquia Support directly for critical cases.

Unreachable scope

• External systems outside Acquia Cloud Platform, such as browser rendering, CDN behavior, and third-party scripts.

• Cron job diagnoses. The agent reads cron logs as evidence but does not diagnose cron jobs.

• Audit logs or user activity logs.

• Applications hosted outside Cloud Platform.

• Raw log content. The agent reports identified patterns and evidence instead of raw log lines.

Governance and control limits

• No automatic reversal: A revert operation requires the same approval process as any other change.

• No activity record: No customer-visible record of agent activity is provided.

• No per-user capability limits: The agent role applies to the entire project, so every user with access can delegate the same set of tasks.

• Fixed Source CMS configuration: Source CMS provides no edits to the agent role or permission set. An administrator configures site access only.

• Global connector settings: Users with Administrator role can turn a connector on or off. Connector settings apply to the whole organization.

Scope and reach

• Single-target operations: Tasks run on one site or one application at a time without batch actions across multiple sites.

• Acquia Source CMS restriction: Site work applies to Acquia Source CMS sites only.
  

  Note

  Custom Drupal applications hosted elsewhere cannot connect in this release, though Acquia plans a contributed module for Drupal 11 and later.

• Connector limits: Slack serves as the sole connector.

Acquia DAM boundaries

• The agent returns matching assets with a preview, metadata, usage rights, and links, within the permissions a DAM administrator has granted. A user can also update assets.

• Cannot search across two DAM accounts in a single request.

• Accesses the Assets application only, excluding Entries, Templates, and Workflow.

• Does not extend permissions beyond limits configured by a DAM administrator.

Governance check limits

• Performs no SEO scans.

• Performs no data protection scans.

• Runs checks only on request, without automatic pre-publication checks.

• Fixes apply only to custom components on connected Acquia Source sites for a reviewed set of common accessibility errors.

Agent role and permission set

The agent holds a dedicated Agents Team role, separate from human user roles. Roles consist of independently configured permissions:

• Cloud Platform: An administrator configures exact permissions for the Agents Team role per environment.

• Source CMS: The agent holds a fixed member role that cannot change. Source CMS provides no permission controls for the agent, so administrator configuration remains limited to site selection.

• Acquia DAM: A DAM administrator configures agent visibility scope directly inside Acquia DAM Admin Tools rather than Acquia AI. The permission set of the agent cannot exceed the permissions of that administrator.

The agent holds permissions only on applications and sites assigned to the Agents Team. Capabilities outside this assignment remain unavailable.

Governance and control management

Organization structure: Organizations hold one project and one Agents Team.

Organization structure: Organizations hold one project and one Agents Team.