Overview
The ARIA Automation Center controls how ARIA is allowed to work.
Use it to set the normal autonomy level for each operational area. Then use ARIA Operations to supervise the work ARIA creates.
Operational packs
ARIA groups related work into operational packs such as:
- Front Desk
- Client Relationships
- Scheduling
- Sales and Retention
- Marketing
- Billing and Payments
- Documents
- Events
- Staff and Payroll
- Retail and Inventory
- Studio Health
Autonomy levels
Each pack has one autonomy setting:
- Handle automatically: ARIA uses the maximum safe autonomy allowed by the rules in that pack.
- Prepare for my review: ARIA prepares work and stops for staff review when needed.
- Notify me only: ARIA surfaces the issue without taking the next step.
- Off: ARIA does not create new work from that pack.
Rule exceptions
Individual rules inherit their operational pack.
Only create a rule exception when that specific workflow should be more restrictive than the rest of the pack.
A rule can never become more permissive than its pack.
Autonomy is not the same as delivery permission
Choosing Handle automatically does not automatically give ARIA permission to send an email or text message.
External delivery still depends on the underlying rule being explicitly allowed to send.
Financial safety
Billing and Payments can be set to Handle automatically for safe detection, preparation, and permitted communication.
ARIA still cannot automatically:
- Charge a payment method
- Retry a failed payment
- Issue a refund
- Waive a balance
- Mark a payment paid
- Create a payment transaction
- Change financial access or payment status
Best practice
Start with DanceFlow's recommended pack settings. Change a pack only when your studio needs a different boundary, and use rule exceptions sparingly.