Current public status
Available in supported workflows after the workspace is configured.
The record explains Aptoria’s workflow; it is not a substitute for a customer’s legal, accounting, or regulatory recordkeeping obligations.
A control only applies where the action is run through the supported Aptoria workflow.
Availability boundary
Published status
Available
Provider or jurisdiction
Not represented here
Result
No outcome promise
Controls before use
Configuration, provider setup, and a reviewable record matter more than a feature-page promise.
Actions, policy changes, and approvals are designed to remain reviewable in the workspace.
The system preserves a human-required floor for defined consequential action classes.
Control check
Source records
Reviewable
Policy
Configured by owner
Exception path
Human owner
When Aptoria pauses
When a record is incomplete, conflicting, or outside policy, the action should pause and be assigned to a human owner.
Do not treat a draft, sample, or activity entry as proof of delivery, settlement, legal validity, or compliance.
Use the Trust Center and Availability pages for the current workflow boundary before enabling a customer-facing process.
Escalation
Sensitive or uncertain
Pause and review
Decision owner
Authorized human
Record
Keep evidence with workflow
Trust without theater
Verifiable, not vibes.
Three things you can check yourself — without a sales call, without a logo carousel.
See exactly how we measure it
Switching from another tool?
Review the workflow before relying on it.
Aptoria publishes availability, controls, and human boundaries instead of treating a feature page as a provider, legal, security, or outcome guarantee.