In Work mode, users describe the work, the agent proposes a plan, and the agent takes no action until plan approval. Publication requires a second, separate approval.
Two approval points exist in the workflow:
Plan approval: Before starting work, the agent states its intent. Users can request changes. The agent proceeds only after plan approval.
Publication approval: Publication requires a second approval. Plan approval does not publish the result.
Prerequisites
Ensure that the setup meets the following requirements:
The account holds Acquia AI access and Work mode permissions.
An administrator assigned the agent to the target application or site.
The subscription holds an available AI credit.
Delegate a task
To delegate a task:
Open Acquia AI and set the mode toggle to Work mode.
Describe the work in plain language. Name the site or application, the intended outcome, and applicable constraints. For example: On the campaign site, add a page for the autumn promotion, with our standard hero and two feature blocks.
Add required context groups, such as brand guidelines or approved copy.
Submit the request.
Answer clarifying questions from the agent. A short initial exchange produces closer alignment than a single complex instruction.
To learn about how Work mode operates with Acquia Cloud Platform, visit Use Acquia AI with Cloud Platform applications.
Approve the plan
The agent states its intent before taking action. Review this intent statement rather than expecting finished output:
Read the proposed plan. Verify the specified page, component, and site.
Approve the plan to let the agent proceed.
Request and describe changes if necessary. The agent revises the plan and presents it again.
Reject the plan to stop the task.
Plan changes at this stage require fewer resources than corrections after work creation.
Approve publication
The agent generates a draft result. Publication requires a separate approval, so plan approval alone does not display results to site visitors.
When Slack integration is configured, Acquia AI sends a Slack notification when the result reaches review status. Review and approval must occur in Acquia Source.
To approve publication:
Inspect the draft directly rather than relying solely on the agent summary.
Run a governance check before publication. For additional details, visit Run a governance check and apply a fix.
Approve publication or request revisions.
Review requirements before publication
Consider the following factors before publication approval:
Current releases do not include automatic reversals. Reverting a published change follows standard change processes.
Review the entire result instead of relying on summaries. Read the draft directly.
Revisions consume AI credits. Correcting a plan during initial approval costs less than multiple correction cycles after work creation.
Permanent agent limits
Even with approval, the agent cannot perform the following actions:
Modify application code.
Modify infrastructure configurations.
Take direct action on a diagnosis. Diagnoses return findings and recommended next steps for code owners to apply. For additional details, visit Diagnose a slow or failing application.
For additional details, visit Governance and control management.
Zero credit balance behavior
When credit balances reach zero, new tasks cannot start until the balance resets on the first day of the following month or until the account team adds credits. In-progress tasks complete without interruption, and review, approval, or publication options for existing results remain available. For additional details, visit AI credits and usage.
Delegate and approve a task in Work mode
In Work mode, users describe the work, the agent proposes a plan, and the agent takes no action until plan approval. Publication requires a second, separate approval.
Two approval points exist in the workflow:
Plan approval: Before starting work, the agent states its intent. Users can request changes. The agent proceeds only after plan approval.
Publication approval: Publication requires a second approval. Plan approval does not publish the result.
Prerequisites
Ensure that the setup meets the following requirements:
The account holds Acquia AI access and Work mode permissions.
An administrator assigned the agent to the target application or site.
The subscription holds an available AI credit.
Delegate a task
To delegate a task:
Open Acquia AI and set the mode toggle to Work mode.
Describe the work in plain language. Name the site or application, the intended outcome, and applicable constraints. For example: On the campaign site, add a page for the autumn promotion, with our standard hero and two feature blocks.
Add required context groups, such as brand guidelines or approved copy.
Submit the request.
Answer clarifying questions from the agent. A short initial exchange produces closer alignment than a single complex instruction.
To learn about how Work mode operates with Acquia Cloud Platform, visit Use Acquia AI with Cloud Platform applications.
Approve the plan
The agent states its intent before taking action. Review this intent statement rather than expecting finished output:
Read the proposed plan. Verify the specified page, component, and site.
Approve the plan to let the agent proceed.
Request and describe changes if necessary. The agent revises the plan and presents it again.
Reject the plan to stop the task.
Plan changes at this stage require fewer resources than corrections after work creation.
Approve publication
The agent generates a draft result. Publication requires a separate approval, so plan approval alone does not display results to site visitors.
When Slack integration is configured, Acquia AI sends a Slack notification when the result reaches review status. Review and approval must occur in Acquia Source.
To approve publication:
Inspect the draft directly rather than relying solely on the agent summary.
Run a governance check before publication. For additional details, visit Run a governance check and apply a fix.
Approve publication or request revisions.
Review requirements before publication
Consider the following factors before publication approval:
Current releases do not include automatic reversals. Reverting a published change follows standard change processes.
Review the entire result instead of relying on summaries. Read the draft directly.
Revisions consume AI credits. Correcting a plan during initial approval costs less than multiple correction cycles after work creation.
Permanent agent limits
Even with approval, the agent cannot perform the following actions:
Modify application code.
Modify infrastructure configurations.
Take direct action on a diagnosis. Diagnoses return findings and recommended next steps for code owners to apply. For additional details, visit Diagnose a slow or failing application.
For additional details, visit Governance and control management.
Zero credit balance behavior
When credit balances reach zero, new tasks cannot start until the balance resets on the first day of the following month or until the account team adds credits. In-progress tasks complete without interruption, and review, approval, or publication options for existing results remain available. For additional details, visit AI credits and usage.
Source