Menu
Help centre

Review an AI action before confirming it

A confirmation is the decision point for supported financial or access-changing AI actions. The preview must match the work you actually intend to perform.

Before you start

You need the relevant module and action permissions. Have the source information ready so you can verify the proposal independently.

Follow these steps

  1. Read the action name and proposed details.
  2. Check the client or employee, item IDs, amounts, dates and applicable fields.
  3. Compare the proposal with existing records to avoid duplicates.
  4. Cancel if anything is unclear; use the manual screen to investigate.
  5. Confirm only when correct, then inspect the resulting record and status.

Check the result

A successful confirmation can create or post real records, including supported invoices, expenses, payroll or custom roles. It is not necessarily a draft-only save.

If you get stuck

If the action is blocked, read the permission or validation message. If the result is uncertain after a timeout, inspect the records before asking AI to run it again.

One thing to remember

A generated custom role is not automatically assigned to a user. Confirmation also does not certify that the business decision, tax treatment or amounts are correct.

Keep going

Company AI connection

Useful assistance with a deliberate review.

  1. Consent and user task
  2. Bounded authorised retrieval
  3. Configured external provider
  4. Response / proposed action
  5. Human review
  6. Cancel or edit
  7. Confirm supported action
  8. Inspect result

Still need a hand?

Tell us what you tried, what you expected and what happened. Keep passwords, API keys and private customer information out of your message.

Open a support ticket. Visitors without a workspace can contact us.

Still stuck?

Before contacting support:

  1. Confirm the workspace, record number, date range and status.
  2. Check your role permissions and the source document.
  3. Refresh once and search for the record before repeating a submission.
  4. Check the relevant guide for the next action; do not force a match, posting or approval.

If you still need help, include the page address, exact message, time, expected result and checks already completed. Never send passwords, API keys, payment-card details or provider secrets.

Was this article helpful?