Aptoria helps coordinate supported property-management workflows inside configured policy and provider boundaries. This page describes three product controls: the action classes kept human-required, the eligible pending actions that can use a soft-commit cancellation window, and the operational records Aptoria keeps for supported workflows. These controls reduce risk; they do not certify legal compliance, guarantee an external outcome, or replace a customer’s own records and professional review.
What we’ll cover
The human-required floor — defined consequential actions Aptoria does not autonomously execute
The soft-commit workflow — a cancellation window for eligible pending actions
Action history — reviewable records with available verification context
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. The Human-Required Floor
Aptoria’s current execution controls keep defined consequential action classes on a human-required floor. Customers are not offered a setting that enables autonomous execution for these classes. Aptoria may organize source records, identify a review step, or prepare a draft, but the authorized person retains the decision and any required external process.
Human-required action classes include:
Action class
Aptoria’s limited role
Eviction or possession action
Organizes available account and communication records. The decision, notice review, filing, and legal process remain with the responsible person and qualified adviser.
Applicant denial or adverse action
Can organize available application records. An authorized human uses an appropriate screening process, makes the housing decision, and handles required notices.
Security-deposit deduction
Can prepare a review package from configured records. A responsible human determines the deduction, reviews jurisdiction-specific requirements, and authorizes the outcome.
Fair-Housing-sensitive or accommodation matter
Routes the matter for human handling when a supported workflow identifies sensitive content. Product routing is not a legal determination 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
Eligible irreversible autonomous actions routed through Aptoria’s soft-commit workflow receive a 15-minute cancellation window before execution. The pending record shows when that control applies. Standing-authorized workflows, provider-managed operations, and actions already completed outside the pending state can follow different authorization, settlement, cancellation, or remedy rules.
What the window does — and does not do
When an eligible action is still pending and the cancellation control is available, cancelling it prevents that Aptoria soft-commit execution. Notification delivery and the availability of the control depend on the configured workflow.
The window is not a universal hold on payments, messages, vendor work, or provider operations. It cannot reverse a provider or external action that has already completed; corrections, refunds, disputes, and other remedies follow the applicable workflow and provider process.
Other supported actions follow their published approval and escalation rules. Review the action class, provider state, policy, and current status before relying on a cancellation control.
3. Reviewable Action History
Supported Aptoria workflows record available action, policy, approval, and outcome context in the workspace. Some supported records include hash-chain verification context that can help reveal a later mismatch. Coverage depends on the record type and workflow; an activity entry is not 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 establish 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.
Where export is supported, review the export scope and available verification details before relying on it.
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 through supported Aptoria controls. Soft-commit can add a cancellation opportunity to eligible pending actions. 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.
Use a non-consequential test to confirm the human-required path and escalation owner.
For an eligible soft-commit action, inspect the pending status and test cancellation before production reliance.
Inspect the resulting activity record and compare it with the source and provider records.
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 applies to eligible pending actions, not universally to provider or external operations.
Action history is a reviewable operational record with workflow-dependent verification context, not a legal or compliance certification.
Evaluate each workflow against its current configuration, provider state, limits, and responsible human owner before relying on it.