Overview
ARIA is designed to handle routine work while keeping higher-risk decisions under studio control.
Each operational pack has an autonomy level.
Handle automatically
ARIA handles everything it safely can within that operational area.
This does not mean every action is automatic.
A rule may still require review because of risk, missing information, or delivery restrictions.
Prepare for my review
ARIA can detect the issue, gather the relevant information, and prepare the next step.
Staff reviews it before the workflow continues where approval is required.
Notify me only
ARIA surfaces the issue but does not prepare or execute the next step.
Off
ARIA does not create new work from that operational pack.
Rule-level exceptions
Rules inherit the pack setting by default.
A rule exception can make one workflow more restrictive.
A rule cannot be more permissive than its operational pack.
External communication is separate
Autonomy and external delivery are separate permissions.
A pack being set to Handle automatically does not give every rule permission to send email or SMS.
A communication is sent automatically only when the underlying rule explicitly allows external delivery.
Financial decisions are always staff-controlled
ARIA cannot automatically:
- Charge a card or payment method
- Retry a failed payment
- Issue a refund
- Waive a balance
- Mark an outside payment as paid
- Create a payment transaction
- Change financial access or payment status
ARIA may identify a payment exception, prepare a follow-up, or send a permitted reminder. The financial decision itself remains with studio staff.
Scheduling and other higher-risk work
ARIA can identify schedule conflicts, missing instructor coverage, or other operational problems.
It does not automatically move or cancel appointments when staff judgment is required.
Best practice
Use Handle automatically for routine work you trust ARIA to manage safely, and let rule-level safeguards stop ARIA wherever a decision still belongs to your team.