Aptoria
Features
Product
Resources
Company
Tools
Log in
See the demo
Help center
The AI agent
Setting autonomy thresholds
Spend caps, approval thresholds, and the actions that can never be automated no matter how you set the dials.
The short answer
Set autonomy thresholds in Settings → Agent by choosing which routine actions can run, then placing per-action, daily, and monthly spend limits around them. Work inside those limits can proceed; anything over them routes to the approval queue. Some consequential actions, including applicant denials, evictions, and lease terminations, always require a person.
Workflow at a glance
1
The master switch and the basic dials
2
Per-task spend limits
3
The blocked floor — never automated
4
The emergency stop
The master switch and the basic dials
Everything the agent can prepare starts off under Settings → Agent. The master autonomy switch decides the default posture: with it off, the agent only proposes actions and you approve every one; with it on, eligible routine work inside your limits can move through the configured review and safety-window workflow. Autopilot is a one-click preset that flips the switch and the relevant dials to a conservative starting point.
The same screen holds the everyday dials: auto-reply to tenant messages (with categories and escalation keywords), maintenance triage, a dispatch-review cost cap, and a "waive small late fees under $X" allowance. Set a cap to 0 to always require your approval for that action.
Per-task spend limits
For finer control, Settings → Agent → Per-task spend limits lets you cap autonomous spend by task category: repairs and dispatch, approvals, late fees, late-fee waivers, lease renewals, and rent collection. Each category has a per-action cap plus optional daily and monthly ceilings — leave a field blank for no limit of that kind.
Under a cap, eligible actions can enter the configured safety-window workflow; over it, the action routes to your review queue. Daily and monthly ceilings count actions still inside their safety window too, so a burst can't slip past the limit. Repairs can additionally be restricted to your preferred vendors, and renewal drafts are bounded by a maximum rent-bump percent.
The blocked floor — never automated
Some actions are never autonomous, regardless of plan or threshold. These are the compliance and liability floor, and no setting or custom rule can promote an action past its lock.
They include: denying an applicant (FCRA requires a human decision plus an adverse-action notice), filing an eviction, terminating a lease, moving a large sum in a single transfer, refunds above a set amount, the Fair Housing check on every AI message, the audit log, and TCPA quiet hours. For these the agent can draft, remind, and tee up the decision, but the decision stays with you.
The emergency stop
If something ever looks wrong, the emergency stop on the Agent screen pauses all autonomy at once and voids anything sitting in its safety window. Your configuration is preserved — everything routes to your review queue until you resume. Every autonomous action is also logged and, where reversible, undoable from the agent activity feed.
Related articles
The AI agent
Using the approval queue
How proposed actions reach you to approve or deny, and how the soft-commit window lets you intercept an automatic action before it lands.
Rent collection
How autopay works
How a tenant turns on autopay, when rent is pulled, and what happens if a payment fails.
Security & compliance
Security and your data
Turn on two-factor authentication, manage sessions and backup codes, export your data, and review the audit trail.
Didn't answer your question?
Email support@aptoria.ai and a person will help — no ticket queue, replies within 24 hours on weekdays.
Email support
Back to Help center