# Approvals and rules

Nothing leaves Dija unapproved. Dija runs read-only lookups right away, while every action that creates, edits, sends, deletes, or uploads data in a connected tool waits for human approval unless an **Allow** rule permits it. Both the **Do not contact** list and **Never** rules always take priority, even over manual approval.

If Dija cannot confirm that a tool call is strictly read-only, it treats the call as a write and asks first.

## How approval requests work

While an action waits for review, the job continues any other steps that do not depend on it. Dija sends the request to the responsible teammate's channel beginning with `"Approval needed"`, grouping multiple requests from the same job into a single message.

Every summary shows what the action will do, who it reaches, which tool it calls, and any attached files. Dija generates this summary directly from the tool call's actual parameters rather than letting the AI model describe its own action, keeping the summary identical across every channel.

- **In button-enabled channels:** A single request offers **Approve**, **Change**, **Reject**, and **Always allow**. A batch offers **Approve all** (covering only the items shown in that message), **Read them**, **Reject all**, and **Always allow**.
- **In the web app:** [Approvals](https://app.dija.ai/approvals) organizes requests under **For you**, **Team**, and **Decided**.

## Approving, editing, or rejecting

- **Approve:** Runs the action immediately. External messages cannot be recalled once sent.
- **Change:** Edit the payload before running it. On **Approvals**, click **Change**, update the fields, and click **Run with these changes**. In chat, click **Change** or describe what to adjust; Dija sends back the complete updated request for confirmation before running it.
- **Reject:** Click **Reject** in a channel to decline immediately, or reply with your reason so Dija adjusts its work.
- **Deciding in plain words:** You can also approve or reject in chat using your own words. Before running anything, Dija posts an exact read-back of what your confirmation will execute, and only a clear `"yes"` from you within 30 minutes confirms it.

## Ownership and automatic escalation

Each request routes to the teammate who owns the record being worked on (when identified), otherwise to the person who started the job, or to the workspace owner for background event jobs. That person, anyone above them in their reporting chain, and the workspace owner can decide it.

Unanswered requests never stall silently:

1. After **2 working hours**, Dija reminds the reviewer.
2. After **4 working hours**, the request escalates to their manager, continuing up the reporting chain every 4 working hours until it reaches the workspace owner.

Only working days and working hours count, which the owner configures under **Settings** > **Approvals that wait**. If a job fails or is cancelled, its pending requests are withdrawn and reviewers are notified.

## Setting and revoking rules

To stop approving routine actions one by one, say `"From now on, you don't need to ask me before..."` in chat, or click **Always allow** (**Always allow requests like this** on **Approvals**). Dija drafts a rule from your words, shows any existing rule it would replace, and waits for your confirmation before activating it. Once you confirm an **Allow** rule, Dija also approves the requests already waiting that the rule now covers.

After you approve the same kind of request in your channel three times in a row without changing it, Dija offers once to handle that kind of request without asking you. It makes no offer for a kind of action that a rule already covers or that a rule you revoked once covered.

Each rule sets one of three outcomes: **Allow** (runs automatically), **Ask first**, or **Never**.

- **Who a rule covers:** You can set rules for your own work. Managers and the owner can also set rules for a specific person below them or everyone below them.
- **Which rule wins:** Rules set higher in the reporting chain win first, followed by the more specific rule, followed by **Never** over **Ask first** over **Allow**.
- **Safety guardrails:** Dija refuses blanket rules that would allow every action without asking. Outbound sends can run unasked only when every recipient is a verifiable address (such as an email address or phone number) that can be checked against **Do not contact**.

To remove a rule, say `"Ask me again about..."` in chat or click **Revoke** on [Rules](https://app.dija.ai/rules) (available to whoever created the rule and anyone above them). Revoking an **Allow** rule takes effect right away; revoking an **Ask first** or **Never** rule widens what Dija can do, so Dija reads the change back and waits for your confirmation.

## Verified channels only

Written confirmations and rule changes count only when they come from you in an authenticated channel (a colleague's `"yes"` to your read-back has no effect). Because live phone calls and external MCP assistants like Claude or ChatGPT cannot prove who is speaking, Dija never approves requests or changes rules there; instead, it sends the approval card to your verified channel so you can decide with its buttons.

## Do not contact and Undo

- **Do not contact:** Listed on **Rules**, this blocklist stops Dija from reaching specific email addresses, domains (including all subdomains), phone numbers, or profile URLs. Every argument of every tool and channel call is checked against it, overriding both rules and manual approvals. Anyone on the team can add an entry; only a manager or the owner can remove one.
- **Undo:** On the **Decided** tab of **Approvals**, reversible tool actions show an **Undo** button. Undoing an action runs through the same rule and approval checks, and is available to the action's owner or anyone above them.
