Review Agent actions and approvals

DocuWriter separates answering a question from changing your workspace. The Platform Agent can perform permitted reads directly; changes and generator runs are prepared for your review.

Review a proposed action

An approval can identify the target Space, document, repository link, team member, or integration, together with the requested change. For document edits, inspect the content or diff. For a generator, check its inputs and credit impact. For sharing, check what will become accessible through the resulting public link.

Approve to execute the proposal or reject it to leave the resource unchanged. Rejection is useful when you want to refine the request: explain the correction and ask for a new proposal. Do not approve an action merely because its title resembles your request; inspect the actual target and content.

Access and freshness are checked again

An approval does not override your account role, plan, or resource permissions. DocuWriter checks the action when it executes. A proposal can become stale if the page, membership, or relevant settings changed after it was prepared. Ask for a fresh proposal rather than repeatedly submitting the old one.

Support requests are also drafts until confirmed. A browser handoff can be required for authentication, account settings, downloads, or selection/review steps that cannot be completed in the conversation.

MCP assistants have their own confirmation controls

The web and Slack Platform Agent show DocuWriter approval interfaces. External MCP assistants use their client's tool-approval and confirmation settings. Do not assume a second DocuWriter approval card will appear after an MCP write tool is called. Ask the assistant to show its proposed change first and configure its permissions accordingly. DocuWriter still enforces server-side authorization.

Check the result before retrying

A pending approval is not a completed action. A started background workflow is not finished documentation. If a connection drops after an action, inspect the target resource or generation history before asking for another run. This avoids creating duplicate pages or spending credits twice. Slack provides additional stop and recovery behavior described in the Slack guide.