Agent actions and approvals

The Platform AI Agent can search, explain, and prepare work across DocuWriter.ai. What you see depends on where you use it: the DocuWriter web Agent, the private Slack Agent, or an external assistant connected through DocuWriter MCP.

The same DocuWriter permissions and product rules remain authoritative on every surface. A chat message, Slack workspace membership, or MCP connection never grants access by itself.

Three types of actions

1. Reads and guidance

Read-only requests can complete without an action approval.

Examples:

• Search and read documentation
• List Spaces, folders, pages, generations, suggestions, team members, or integration status you can access
• Search linked source code
• Show available generators or an existing full-tree preview
• Search DocuWriter platform guides
• Show Space activity when your plan includes it

The Agent checks current access when it performs the read. A page or Space mentioned earlier in a conversation does not bypass a later permission change.

2. Changes that require approval

The Agent prepares an action first. Nothing changes until you review and approve it.

Examples:

• Create or update a page
• Create, update, move, copy, share, or delete Space items
• Apply, discard, snooze, or bulk-manage Autopilot suggestions
• Create or change an Autopilot repository link
• Rename, archive, restore, share, or add a generation to a Space
• Create, update, or delete a webhook
• Change AI preferences
• Invite, change, remove, or cancel an invitation for a team member
• Revoke a connected Git provider
• Start a generator
• Send a support request

Approval is not the same as execution, and execution is not the same as confirmed delivery. After approval, DocuWriter rechecks identity, membership, resource access, current resource version, plan or credit requirements, policy, and destination. The result tells you whether the action succeeded, failed, needs to be tried again safely, or has an outcome that must be confirmed before any retry.

3. Browser-only setup or continuation

Some work requires an external authorization page, file or repository selection, payment confirmation, download, or another browser-only step. The Agent explains the requirement and opens the correct DocuWriter page.

Examples:

• Connect GitHub, GitLab, Bitbucket, Azure DevOps, or self-hosted GitLab
• Select a repository, branch, files, or an accepted full-tree documentation structure
• Upload individual files, preview images, or a one-time project ZIP for Full Tree Documentation
• Manage billing, invoices, subscription changes, cancellation, password, or API-token secrets
• Authorize Confluence or another external account
• Download files
• Complete a large or sensitive approval that cannot be presented safely in chat

For full-project documentation when a Git provider cannot be connected, the Agent can guide you to Full Tree Documentation → Upload a ZIP instead. This is a secondary browser-only path for a .zip archive up to 20 GB. It creates a one-time snapshot and does not enable webhooks, automatic code-change detection, Autopilot repository sync, pull-request comments, or branch-based release notes.

Opening a page does not perform the action. Sensitive continuations use a short-lived, single-use handoff bound to the signed-in DocuWriter account and exact operation.

How approval differs by surface

Surface	Conversation and review	Where approval happens
DocuWriter web Agent	The conversation is saved in DocuWriter. Changes appear as a preview or diff in the Agent panel.	Review and approve or reject in DocuWriter. Web bulk review controls apply only where the web UI offers them.
Slack Agent	The full Agent runs only in a private conversation with the DocuWriter Slack app. Slack context is fetched transiently and is not saved as a DocuWriter transcript.	Review the private Slack approval message and select Approve or Reject. If Slack cannot safely present the complete action, use the exact secure DocuWriter handoff it provides.
MCP assistant	The external assistant uses one of DocuWriter's separate MCP tools. Its conversation storage depends on that assistant, not the Platform Agent conversation store.	Review and authorize the mutating tool call in the MCP client. The client confirmation is separate from a web or Slack Agent approval message.

A decision on one surface cannot broaden the original action. Repeated or simultaneous decisions converge on the same stored action outcome; DocuWriter does not intentionally run the same approved change twice.

Slack approval safety

Slack approvals are bound to the linked Slack identity, private destination, original bot-authored approval message, exact action, resource version, and current workspace policy.

DocuWriter does not store the approval content copied from Slack. It keeps opaque references, versions, counts, and a keyed digest so it can verify that the complete bot-authored proposal still matches at decision time.

An approval is rejected or marked stale when, for example:

• another Slack user selects the button;
• the action comes from a different conversation or message;
• the proposal fragments changed or are missing;
• the DocuWriter account, team membership, resource access, or policy changed;
• the target resource version changed;
• the Slack installation, token, permissions, or private destination is no longer valid.

Ask the Agent to prepare a fresh action after a stale approval. It does not reconstruct or rerun a change from an untrusted quoted message.

Generators

The Agent can route all supported generator families when the required inputs are available. Starting a generator requires approval.

Most synchronous generator results can return in the current Agent conversation. Codebase documentation and full-tree documentation are long-running workflows: Slack confirms the start and directs you to DocuWriter for current progress or review.

If required provider authorization, repository import, file selection, full-tree generation/review, or upload is missing, the Agent gives browser guidance instead of pretending the generator started. For a one-time project ZIP, the user completes the upload and initial tree review in Full Tree Documentation.

Support requests

The Agent prepares the support message for review. A support request is sent only after its own approval and is never included in a general Approve All action.

DocuWriter reports “sent” only after confirmed delivery. A timeout after possible acceptance is not silently treated as success or retried in a way that could send a duplicate.

Stop, retry, and uncertain outcomes

Before a side effect begins, an eligible Slack request can be stopped with its Stop control or an exact stop or cancel message.

After a change or external request may have been accepted, DocuWriter preserves the authoritative or uncertain state. It does not claim cancellation, replay the Agent, or blindly repeat the action.

If final Slack delivery fails:

• a safe read can be requested again;
• an existing product artifact remains available in its normal DocuWriter location;
• a confirmed or uncertain change is reconciled instead of repeated automatically.

Platform Agent tools and MCP tools are different

The Platform Agent currently has 22 grouped capabilities. A group can cover several read, guidance, proposal, or generator operations.

DocuWriter MCP currently exposes 72 separate tools for external assistants. The counts describe different interfaces and should not be compared as if Slack had fewer product actions. The Slack Agent does not invoke or duplicate MCP wrappers; it runs the shared Platform Agent and the normal DocuWriter authorization and action services.

See Slack Agent for installation, account linking, private conversation behavior, privacy, team controls, cancellation, and unlinking.

For the separate external-assistant interface, see MCP Tool reference guide.