Skip to main content
A proposal is a change that an agent has prepared but Docket has not applied. The proposal stays attached to the agent session that produced it.

Read the proposed change

The proposal card names the action and shows the affected fields. Proposed Tasks can also appear as ghost rows in the work view where they would be created. Check the object, workspace, assignee, dates, and relationships before you approve the change.

Edit a supported proposal

Change supported fields in the proposal before approval. Docket applies the edited input, not the agent’s first draft. If the proposal cannot express the change you need, reject it and tell Athena what to draft instead.

Approve or reject

You can decide one action or an entire proposal group. A rejected action does not run later.

Act from the session or Inbox

The session is the complete review surface. Inbox can show an approval request and offers a direct approval action for supported low-risk requests. Acting in either place updates the same underlying approval.

Understand the approval setting

Your Settings → Athena choice controls the normal behavior:
  • Ask before acting pauses on actions that require your decision.
  • Routine autonomy allows routine, reversible work and keeps gates for higher-risk actions.
  • Suggest only records proposals without applying them directly.
Agent, Team, and workspace rules can add narrower controls. Permissions still apply after approval.

Keep ownership clear

Docket records Athena as the actor and records the person on whose behalf Athena worked. Assign yourself and use Athena as the delegate when you remain accountable for the Task. Email task suggestions use their own accept, edit, and dismiss flow. See Athena and your mail.