Skip to main content
Trust
Trust

Aptoria Trust Spine System Card: Boundaries, Intercepts, and Action Records

Aptoria is AI property management software for landlords and small-to-mid-size property-management firms. This plain-language system card covers the actions Aptoria prohibits or requires humans to review, the cancellation window planned for money movements, and the records Aptoria keeps.
Updated October 2026
Aptoria
Trust
1. Prohibitions and Human Review
2. The Soft-Commit Workflow
3. Reviewable Action History
4. Product Control Specification
Why These Boundaries Matter
How to Evaluate the Controls
5
What we’ll cover
3
Key takeaways
5
Frequently asked
9
Trust
Updated October 2026
1
1. Prohibitions and Human Review
Aptoria has 14 hardcoded limits no setting can switch off: 8 actions always require a human, and 6 are prohibited outright. Aptoria’s current execution controls keep those published consequential action classes on a restricted floor. Customers are not offered a setting that enables autonomous execution for these classes. The authorized person makes the decision and runs any required external process.
2
2. The Soft-Commit Workflow
When rent payments are enabled, eligible pending money movements will have a 15-minute cancellation window; no money moves through Aptoria today. Aptoria doesn’t carry out routine work on its own yet. Today you can set the limits it will work within, and its hardcoded limits are published. The window is part of the planned payment workflow: an eligible pending action will wait 15 minutes before it runs, and cancelling it in that time will stop it.
3
3. Reviewable Action History
Nothing runs on its own in Aptoria today, so there are no agent actions to record yet. When agent actions are enabled, each will be recorded with its policy, approval, and outcome context, and some records will carry hash-chain context that can help reveal a later mismatch. Coverage will depend on the record type and workflow; an activity entry will not be proof that an external provider delivered, settled, filed, or accepted an action.
4
4. Product Control Specification
A product label such as “AI agent” does not describe what the software may do. The useful specification separates assistance from authority, records the controls that can narrow an action, and identifies the evidence needed to verify an external outcome. This table summarizes the current public control model; availability still has to be checked for the specific workflow and account.
5
Why These Boundaries Matter
Bounded automation is useful when its authority, stop points, and evidence are visible. The human-required floor prevents selected consequential decision classes from being delegated to Aptoria. When rent payments are enabled, the soft-commit window will give eligible pending money movements a 15-minute cancellation opportunity. Action history makes the product’s own workflow easier to inspect. Each control has a defined scope, and none transfers legal or operational responsibility away from the customer.
6
How to Evaluate the Controls
Aptoria Trust Spine System Card: Boundaries, Intercepts, and Action Records
Updated
October 2026
Sections
6
Key takeaways
5
Frequently asked
9
AI Property Management Library
Product availability
Trust Center
The short answer
Is AI property management safe? No product can make that universal promise. Aptoria has 14 hardcoded limits no setting can switch off: 8 actions always require a human, and 6 are prohibited outright. Aptoria reduces specific risks with that floor and with the limits you set. Aptoria doesn’t carry out routine work on its own yet. Today you can set the limits it will work within, and its hardcoded limits are published. These controls do not certify legal compliance. Safety still depends on the property, jurisdiction, provider, configuration, source records, and responsible human judgment.
Key takeaways
Aptoria publishes a human-required floor for defined consequential action classes in supported workflows.
The 15-minute soft-commit cancellation window is planned for eligible pending money movements; no money moves through Aptoria today.
Action history is an operational record, not a legal or compliance certification.
Evaluate AI software with a field-by-field control specification instead of inferring authority from an “agent” or “automation” label.
Human oversight

Humans stay in control.
Agents stay in bounds.

Who can approve what, when the agent can act, and how exceptions escalate.
Review who can approve what
Approval queues
24
↑ 33%
Items waiting for human review
Autonomous actions
247
↑ 23%
Completed within policy
Permission groups
5
Roles across 12 properties
Escalations
3
↓ 50%
Require your attention
You are viewing as Property Manager
You can approve maintenance up to $1,500. Under $500 the agent acts within policy.
Switch role
Permission roles
What each role can see, approve, and manage.
Approval matrix
Who can approve what, before the agent acts.
Request
Owner
Regional Manager
You
Property Manager
Leasing
Accounting
Maintenance over $500
Maintenance over $1,500
Lease renewal exceptions
Vendor onboarding
Late fee waivers
Payment reversals
New property contracts
Under $500 the agent acts within policy. Above it a person decides, within their role’s limit.
Exception routing
Out-of-bounds items move up one role at a time.
1
Aptoria agent
Acts under $500 within policy; flags anything over, non-standard, or in conflict
2
Property Manager
Maintenance above $500, up to $1,500 · routed with a recommendation
3
Regional Manager
Above the Property Manager’s $1,500 limit
4
Owner
High-value or sensitive requests
Each hand-off is logged to the audit trail.
Property Manager
Approval limits for this role.
Maintenance
Up to $1,500
Late-fee waivers
Up to $75
Vendor onboarding
Not in approval path
Lease exceptions
Can approve
Payment reversals
Not in approval path
Recent approvals
Role required, who decided, and when.
Request
Property
Role required
Decided by
When
Status
Grounds service · $1,180
Oakwood Residences · Grounds
Property Manager
Marcus Webb, Property Manager
Mar 28, 9:37 AM
Approved
Lock re-key · $85
Elm Ave Triplex · Unit B
None · within policy
Aptoria agent · within policy
Jun 6, 2:52 PM
Autonomous
Sample portfolio · fictional data
Audit trail

Every decision has a record.

What happened, why, which policy applied, and who approved it — the chain of context Aptoria keeps for supported actions.
Trace a decision in the demo
Sample workspace / Oakwood Residences / WO-77821
Decision timeline
Oakwood Residences · Unit 402 · Maya Rodriguez · every step, who took it, and its status.
10 events
Decision details
Who, what, why, source, rule and result.
Scheduled
Action
Approve repair and create work order
Resident
Property
Work order
Vendor
Amount
$340 · threshold $500
Rule
Approval
Approved
Decided by
Marcus Webb · Just now
Linked messages and files
Why this happened
Resident notified · Aptoria agent · Just now
Residents are told as soon as a repair is approved and scheduled.
Rules applied
1 rule
Resident communication policy
Context used by this step
1 source
Resident thread · Maya Rodriguez
Sample portfolio · fictional data
The short answer
Is AI property management safe? No product can make that universal promise. Aptoria has 14 hardcoded limits no setting can switch off: 8 actions always require a human, and 6 are prohibited outright. Aptoria reduces specific risks with that floor and with the limits you set. Aptoria doesn’t carry out routine work on its own yet. Today you can set the limits it will work within, and its hardcoded limits are published. These controls do not certify legal compliance. Safety still depends on the property, jurisdiction, provider, configuration, source records, and responsible human judgment.

What we’ll cover

The restricted floor — prohibited actions and defined consequential actions requiring human review
The soft-commit window — a planned cancellation window for money movements
Action history — the records Aptoria keeps and what they do not prove
Property-management software can affect money, housing, vendors, and tenant communications. A security page alone does not explain who remains responsible for those outcomes. This public system card describes Aptoria’s current product boundaries so a customer can compare the copy with the configured workflow, provider state, and resulting activity record.

1. Prohibitions and Human Review

Aptoria has 14 hardcoded limits no setting can switch off: 8 actions always require a human, and 6 are prohibited outright. Aptoria’s current execution controls keep those published consequential action classes on a restricted floor. Customers are not offered a setting that enables autonomous execution for these classes. The authorized person makes the decision and runs any required external process.
The current public action classes are generated from the same reviewed product-control registry used by Aptoria’s other trust surfaces:
Action class
Restriction
Reason for the hold
Terminate a lease
Human review required
Ending a tenancy is a judicial-process decision with statutory notice timing — always yours.
File or advance an eviction
Human review required
Possession actions require jurisdiction-specific process and must never be automated from an unsupported legal conclusion.
Deny an applicant
Human review required
FCRA adverse-action rules require human sign-off and proper notice.
Deny an accommodation request
Human review required
Fair Housing Act — only the landlord may decide, with a documented reason.
Deduct from a security deposit
Human review required
Deposit deductions run on statutory clocks with itemization duties — always yours.
Serve a rent-increase notice
Human review required
Notice timing is tiered by tenancy length under state law — served by you, on your decision.
Send a formal collection demand
Human review required
Formal dunning carries consumer-protection formatting duties — never autonomous.
Pool your data to set rents
Prohibited in Aptoria
Your numbers never feed a shared pricing model. Hardcoded — no setting can switch it on.
Set rent from external data
Prohibited in Aptoria
Aptoria policy prohibits automated rent setting from external data, including public-data inputs.
Report a resident to a credit bureau
Human review required
Aptoria does not report residents to credit bureaus today. If it is ever offered, each report would need an authorized person’s decision; no setting, provider, or agent can send one automatically.
Downgrade or close a habitability concern
Prohibited in Aptoria
A model cannot reduce urgency or close a habitability concern without accountable human review.
Override a deposit deadline
Prohibited in Aptoria
Deposit deadlines cannot be extended or suppressed by an agent, workspace setting, or model.
Impose a mandatory fee
Prohibited in Aptoria
The agent cannot create or impose a mandatory fee; enabled fee workflows require separately reviewed authority.
Score a resident’s risk
Prohibited in Aptoria
Proprietary resident risk scores are permanently prohibited. Review source facts and make required decisions as a human.
Approval cannot enable prohibited actions. Human review does not activate a workflow. This boundary is not a legal conclusion or compliance certification.
The floor is an execution boundary for supported Aptoria workflows. It does not monitor activity completed outside Aptoria, establish that a customer’s process is lawful, or remove the customer’s responsibility for the decision.

2. The Soft-Commit Workflow

When rent payments are enabled, eligible pending money movements will have a 15-minute cancellation window; no money moves through Aptoria today. Aptoria doesn’t carry out routine work on its own yet. Today you can set the limits it will work within, and its hardcoded limits are published. The window is part of the planned payment workflow: an eligible pending action will wait 15 minutes before it runs, and cancelling it in that time will stop it.
What the window will and will not do
When rent payments are enabled, the window will apply to eligible pending actions only. It will not be a universal hold on payments, messages, vendor work, or provider operations.
It will not reverse a provider or external action that has already completed; corrections, refunds, disputes, and other remedies will follow the provider’s process.
Undo for autonomous actions is planned; nothing runs on its own today. The emergency stop pauses Aptoria for your whole organization and cancels anything still pending; because nothing runs on its own today, there is nothing for it to stop yet.

3. Reviewable Action History

Nothing runs on its own in Aptoria today, so there are no agent actions to record yet. When agent actions are enabled, each will be recorded with its policy, approval, and outcome context, and some records will carry hash-chain context that can help reveal a later mismatch. Coverage will depend on the record type and workflow; an activity entry will not be proof that an external provider delivered, settled, filed, or accepted an action.
Action history is an operational review artifact, not a complete legal record. It does not prove admissibility or promise acceptance by a court, regulator, auditor, insurer, tenant, or provider. Customers remain responsible for their own retention duties and for preserving source and provider records appropriate to the matter.
When record export is enabled, review its scope and verification details before relying on it.

4. Product Control Specification

A product label such as “AI agent” does not describe what the software may do. The useful specification separates assistance from authority, records the controls that can narrow an action, and identifies the evidence needed to verify an external outcome. This table summarizes the current public control model; availability still has to be checked for the specific workflow and account.
Control field
Current public specification
AI operating model
Aptoria doesn’t prepare routine work for your review yet; its drafting and triage features are planned.
Human gate
The published restricted floor keeps each listed decision with an authorized person.
Permissions
Account settings can narrow what Aptoria will do; they cannot weaken the published floor, sealed constraints, or an active emergency stop.
Spending authority
You can set the limits Aptoria will work within, such as spending caps, in your workspace settings.
Sensitive housing decisions
Applicant denial, accommodation denial, lease termination, eviction, deposit deductions, and the other listed classes stay with a person; Aptoria will never make them on its own.
Evidence and reasoning
When agent actions are enabled, each record will link its policy result, reason codes, source references, approvals, execution state, and provider receipts.
Reversibility
When rent payments are enabled, eligible pending money movements will have a 15-minute cancellation window; no money moves through Aptoria today. Undo for autonomous actions is planned; nothing runs on its own today.
Provider boundary
An internal success state is not proof that a provider delivered, settled, filed, or accepted an external action.
Integration boundary
Most catalogued integrations are planned; a catalog entry is not a connection to your accounts.
Geographic and legal scope
United States-focused educational and workflow support does not mean that a particular action is permitted in a property’s jurisdiction.
This is a product-control record, not a certification of legal compliance, workflow availability, or external outcome.
How to use this specification
For a purchase or implementation review, replace each general row with the exact workflow, property, provider, policy version, responsible person, exception path, and expected receipt. If a field is unsupported or unavailable, stop and resolve it rather than filling the gap with a marketing assumption.

Why These Boundaries Matter

Bounded automation is useful when its authority, stop points, and evidence are visible. The human-required floor prevents selected consequential decision classes from being delegated to Aptoria. When rent payments are enabled, the soft-commit window will give eligible pending money movements a 15-minute cancellation opportunity. Action history makes the product’s own workflow easier to inspect. Each control has a defined scope, and none transfers legal or operational responsibility away from the customer.
That scope is part of the product design: availability can depend on the property, jurisdiction, provider, account, plan, configured policy, and current release. The Trust Center and Availability pages publish the current status and launch requirements for customer-facing workflows.

How to Evaluate the Controls

Review the Trust Center entry for the workflow, including current limits and launch requirements.
Read the published floor and confirm which decisions stay with a person.
Set your limits in workspace settings.
When a planned workflow is enabled, test it with a non-consequential case before relying on it.
Confirm retention, legal, accounting, security, and provider requirements with the responsible professionals and vendors.

Key takeaways

Aptoria publishes a human-required floor for defined consequential action classes in supported workflows.
The 15-minute soft-commit cancellation window is planned for eligible pending money movements; no money moves through Aptoria today.
Action history is an operational record, not a legal or compliance certification.
Evaluate AI software with a field-by-field control specification instead of inferring authority from an “agent” or “automation” label.
Evaluate each workflow against its current configuration, provider state, limits, and responsible human owner before relying on it.
Questions about a specific setup: contact Aptoria and identify the property, workflow, provider, and action class. We will scope the answer to the current configuration and published availability.

Keep reading

What is an AI property manager?
AI Property Management Library
What does autonomous operation mean?
AI copilot: definition and operating boundary
Questions to ask before AI manages your rental
Product availability
Trust Center

Frequently asked

Is AI property management safe?
It can be safer when authority is narrow, consequential decisions stay human-required, pending irreversible actions have clear stop points, and activity is reviewable. Those controls reduce defined risks; they do not guarantee legal compliance or a correct external outcome. Aptoria doesn’t carry out routine work on its own yet. Today you can set the limits it will work within, and its hardcoded limits are published.
Can I trust AI with my rental property?
Trust should be earned workflow by workflow. Start with a low-consequence task, confirm the source records and authority boundary, test the exception and cancellation paths, and inspect the resulting activity record before expanding scope. Keep legal, housing, financial, and emergency decisions with the responsible people and professionals.
What should an AI property manager never do alone?
Aptoria has 14 hardcoded limits no setting can switch off: 8 actions always require a human, and 6 are prohibited outright. Aptoria will never do any of these on its own: terminate a lease, file or advance an eviction, deny an applicant, deny an accommodation request, deduct from a security deposit, serve a rent-increase notice, send a formal collection demand, pool your data to set rents, set rent from external data, report a resident to a credit bureau, downgrade or close a habitability concern, override a deposit deadline, impose a mandatory fee, score a resident’s risk. The human-required classes need an authorized person; approval cannot enable prohibited actions. The spending caps you set are separate from this fixed floor.
Can Aptoria send or advance an eviction notice on its own?
No. Serving an eviction notice and filing or advancing an eviction are blocked execution kinds. The responsible person and a qualified adviser must verify the authority, grounds, content, timing, delivery, service, filing, and jurisdiction-specific process.
How does Aptoria handle Fair Housing-sensitive decisions?
Applicant denials and accommodation-request denials remain human-required; Aptoria never decides on an applicant. AI drafting of tenant and applicant messages is planned; its pre-send housing-language review can miss issues and is not a legal determination. Written criteria, source accuracy, human review, and qualified advice still matter.
Can I configure Aptoria to autonomously execute a human-required action class?
No. No customer setting enables autonomous execution for the published human-required floor. The authorized person makes the decision and runs the external process.
Does the human-required floor mean each routine step needs approval?
No. Aptoria doesn’t carry out routine work on its own yet. Today you can set the limits it will work within, and its hardcoded limits are published. When routine work is enabled, what needs approval will follow the limits you set; consequential decisions on the published floor remain human-required.
Is the action history a legal evidence package?
No. It is an operational record of Aptoria activity. It does not replace source documents, provider receipts, legal records, or professional advice, and acceptance by an external party is not guaranteed.
Does the 15-minute window apply to urgent repair coordination or completed payments?
When rent payments are enabled, eligible pending money movements will have a 15-minute cancellation window; no money moves through Aptoria today. When it is enabled, the window will apply to eligible pending money movements only; provider-managed, completed, and external actions will follow their own timing and remedy rules.

See it run your building.

Aptoria is AI property management software where you set the limits. Plans start at $19/month for up to 5 units. Decisions that matter always stay with you.
Join the waitlist
See the demo