Approvals

Arif uses approvals to keep sensitive work under user control. When a requested action can change business data, safety policy decides whether the action is allowed, blocked, or sent to the user for approval.

Policy Decisions

Decision	Meaning
ALLOW	Arif can run the action if the user has Qriib permission.
ASK	Arif must show an approval card and wait for a user decision.
BLOCK	Arif must not run the action.

Policy can vary by organization, user, operation type, and business record type.

Approval Flow

What Approval Cards Show

Approval cards can include:

The proposed operation.
The affected business record or destination.
A summary of the change.
Important field changes when available.
Approve and reject actions.

Arif waits for the decision before continuing. If the user rejects the request, Arif cancels that action and explains the result.

Saved Preferences

Organizations can allow some recurring approval patterns to be remembered, such as always allowing or denying a specific type of change. Saved preferences still operate inside Qriib permissions and organization policy.

User Guidance

Review approval cards carefully.
Reject changes that do not match your intent.
Ask Arif to explain the proposed action before approving if anything is unclear.
Use Plan mode first for bulk or sensitive work.