Safety and Approvals

The AI Agent uses your existing Blue permissions. It also asks for approval before applicable bulk, destructive, non-reversible, or uncertain actions.

Blue Applies Your Permissions

Blue authorizes AI Agent tools as the person who requested the work. If you cannot view or change an item, the AI Agent cannot bypass that restriction.

This rule applies to:

• The AI Agent panel.
• @Blue requests in record comments.
• Actions that run after approval.

Comments written by the assistant appear under the configured agent name. The requesting person’s permissions still control the action.

Panel Autonomy Modes

Select an autonomy mode in the composer before you send a message:

• Plan: The assistant can investigate and recommend steps. It does not change Blue data.
• Ask: Every write waits for approval in an action card.
• Auto: A reversible, single-item write can run after safety classification. Bulk, destructive, non-reversible, and uncertain writes wait for approval.

For the complete panel workflow, see Using the Assistant.

Approvals in Record Comments

When you mention @Blue in a record comment, supported reversible changes to one item can run immediately. Examples include creating a record or updating one record.

The following requests require a confirmation reply:

• Bulk record updates.
• Bulk custom field changes.
• Destructive actions, including moving records to Trash.
• Non-reversible writes, such as creating lists or changing checklists.

The comment assistant does not perform view-control actions or cross-workspace record moves.

For example, if you ask Blue to move five records to trash, Blue replies with a summary like:

I can move 5 records to trash.
Reply @Blue approve to run it, or @Blue cancel to skip.

Reply in the same thread with @Blue approve to run the pending action. Reply with @Blue cancel to reject it.

Natural replies such as @Blue yes, go ahead also work when they clearly approve the exact pending request.

Ambiguous Replies Do Not Run Actions

If a reply changes the scope, adds a condition, or is unclear, Blue does not run the pending action. It asks for explicit approval or cancellation.

These replies do not approve an action:

• @Blue only the urgent ones
• @Blue wait, which records?
• @Blue maybe later

An approval must clearly refer to the pending request.

Who Can Approve a Comment Action

The person who requested the action can approve it. Organization owners and administrators can also approve it.

If another member replies, Blue does not run the action. Blue explains who can approve it.

Record Deletion Uses Trash

When the AI Agent deletes a record, Blue moves it to Trash. The AI Agent action does not permanently erase the record.

Moving a record to Trash is still destructive because it changes visibility and workflows. Blue requires approval in the panel and record comments.

Multiple Pending Requests

If one request creates several pending actions, Blue treats them as one approval group. One approval runs the complete group.

If a comment thread has pending requests from separate turns, Blue does not select one. Use the AI Agent panel or submit a narrower request.