Aviato / docs
Use Aviato

Actions and approvals

Run business operations and understand when a reviewer is needed.

View Markdown

What an action does

An action is a named operation defined by your development team: for example, tagging an account or generating a document. It can apply to one record, a selection of records, or the collection as a whole.

Select an action, fill in its form, and review the target before running it. An action may return a message, a file, a redirect, or updated records.

The Actions menu lists all actions permitted for your role together. Actions that do not apply to the current selection remain visible in grey; hover over an item or focus it with the arrow keys to see why. Single-record actions need exactly one selected record, bulk actions need at least one, and collection-wide actions are available from the collection view. On a record page, that record is the target for single and bulk actions.

An action can also open from a button in a custom record summary. Developers can compose native custom forms with presets, conditional sections, and live previews. These forms use the same validation, permissions, approval rules, and audit trail as standard action forms.

Approval requests

An approval rule can hold an action for review. A pending request records the action, selected target, form values, and requester. Reviewers inspect the request and approve or reject it according to the rule.

Requests, their history, and CSV exports are visible only to the requester and roles currently allowed to review them. This includes targets, form values, review comments, and execution results.

Approval is not a permanent grant of access. Before execution, Aviato refreshes the requester's membership and role definitions. Removing access can prevent a previously approved action from running.

Approval rules govern custom actions. Direct record creation, editing and deletion use permissions and auditing but do not enter an approval workflow. To require approval for a sensitive write, deny the direct write to that role and expose it as a custom action with an approval rule. Changes made outside Aviato are outside these controls.

The dashboard shows the newest 500 matching requests and indicates when that limit is reached. History CSV export reads all matching pages, up to 100,000 requests or 16 MiB; narrow the date filters if the export exceeds that limit.

Understand the status

StatusMeaning
PendingWaiting for a reviewer.
ApprovedAccepted for execution by the connector.
ExecutingClaimed by a connector; the result has not arrived yet.
ExecutedThe connector reported success.
FailedThe request could not complete successfully.
Rejected / expiredIt will not execute from this request.
UncertainThe action may have run, but its outcome is not confirmed.

An uncertain result needs investigation

Do not immediately submit the same action again. Check the target system and audit activity first, especially for payments, emails, or other external side effects. A stalled execution becomes uncertain after 15 minutes; a late result can still resolve it.

The connector persists completed results and retries reporting them without repeating the action. A crash between an external side effect and its completion record still requires reconciliation.

Developers: make external side effects idempotent where possible and use the SDK integration guides.

Edit on GitHub

On this page