Review and approve AI actions

Prepare a change #

Use Prepare an action to see the catalogue available for your current account. Select a task and complete the structured fields. You can also describe a supported task in chat. Neither path executes a change merely because an answer was generated.

The initial catalogue covers requesting a Basic check from existing credits, assigning a check, adding a note, managing pending invitations, creating or editing teams, changing team membership and updating your notification preferences. Your role can reduce this list.

Inspect the approval card #

Read the action title, target, every proposed field, the current record snapshot and the stated effect. For a real check request, the effect includes reserving an available Basic credit and queueing an invitation. An invitation receipt means it was queued, not proof that an email arrived.

Confirm the correct organisation, check reference, person and role. A similarly named team is not the same team. If anything is ambiguous, revise the proposal before approving. Do not approve a role you are not authorised to grant.

Approve, decline or revise #

Approve authorises only the displayed operation and details. The server rechecks access and current record state before executing the supported service. Decline closes the proposal without making that change. Revise opens the details for editing and prepares a fresh approval card; it does not automatically execute the revision.

Proposals expire. If the underlying state changes, prepare a fresh proposal and review the updated details. A stale or expired card cannot be used to approve an old version of a record.

Read the receipt #

After approval, check the recorded outcome and use Open updated record to verify the result. Repeated approval of an already completed card should return its receipt rather than apply the operation twice. If an action fails, read the reason and inspect the record before creating another proposal.

Keep high-impact decisions in their workflow #

Payments, refunds, signatures, identity decisions, applicant declarations, regulated approvals and elevated access changes are not general chat tools. Follow the dedicated screen’s eligibility, consent, verification and confirmation requirements. A sentence in chat cannot replace these controls.

Detailed walkthrough #

1. Choose the correct operation

Read the offered routine operations and choose the one matching your intended task. Available choices depend on the workspace. If the operation is not offered, use the appropriate product screen rather than asking the assistant to work around permissions.

2. Review every proposed value

Check the operation, selected record and each field in the editor before preparing a real proposal. Similar names can refer to different members or checks. Opening this editor has not saved the proposed change or contacted anyone.

3. Understand approval and retries

A real proposal still needs explicit approval and current permission checks. If the record changes or the proposal expires, prepare a fresh proposal and review it again. Read the resulting receipt before retrying so that a delayed response does not lead you to request duplicate work.

Practise this section #

Open Help & tutorials, select this guide and choose Start practice walkthrough. Read each highlighted component before continuing. Use Back to revisit an explanation and Retry if a sample has not loaded. The walkthrough uses fictional records; do not enter real applicant information.

Use Exit tutorial to leave and keep your place, then Resume walkthrough in this guide to continue. When returning from practice to a real workspace, review the actual record and your permissions before making a change. Tutorial completion does not perform the underlying task.

Before using this guide #

Open AI chat in the intended account perspective. Decide the routine operation and record you want to review; you do not need to approve anything during practice.

Worked example #

To review a team change, check the team identity and proposed name in the editor. If the team has since changed, prepare and review a fresh proposal instead of approving stale values.

Guided component walkthrough #

Each component has one short guided step. Read the explanation, then choose Next; Back revisits the previous component. The cursor only demonstrates useful navigation or an explicit action. Replay action repeats that demonstration, and Skip animation keeps the explanation. Use this written guide for feature details.

Prepare an action

• Prepare an action: The pointer has opened the proposal editor. It lets you draft a routine change and review the operation and values before approval. Opening this editor does not execute a change.

Choose an operation

• Choose an operation: Only routine operations appear here. Regulated decisions are never offered as an AI action.
• Operation choices: The operation choices define what kind of proposal you are preparing. Read their names before choosing: selecting a type only prepares an editor, it is not approval to execute the proposal.
• Choose the correct operation: Read the offered routine operations and choose the one matching your intended task. Available choices depend on the workspace. If the operation is not offered, use the appropriate product screen rather than asking the assistant to work around permissions.

Review before approving

• Review before approving: Opening the editor runs nothing. A proposal waits for your explicit approval before anything happens.
• Proposal fields: Review the proposed target and values together in the action editor. If either is wrong, correct the proposal before approving anything; this guide does not press an approval control.
• Review every proposed value: Check the operation, selected record and each field in the editor before preparing a real proposal. Similar names can refer to different members or checks. Opening this editor has not saved the proposed change or contacted anyone.
• Understand approval and retries: A real proposal still needs explicit approval and current permission checks. If the record changes or the proposal expires, prepare a fresh proposal and review it again. Read the resulting receipt before retrying so that a delayed response does not lead you to request duplicate work.

Related guides