What evidence explains a sensitive action?
A reviewer inspects a journal's retained lifecycle and posting evidence. Audit context complements, rather than replaces, the ledger.
Explore the sample companyAuditability
Trace controlled workflow events, actors, states, and immutable accounting outcomes without exposing secrets.
Access controlsSample company
What evidence explains a sensitive action?
Financial control weakens when access, identity, audit evidence, and sensitive actions are governed by informal assumptions rather than explicit workspace policy.
- Audit trail
- A retained sequence of relevant activity for review; its presence is not itself a certification or external audit.
- What it works with
- Supported scoped audit events, actor and workflow context, and immutable accounting outcomes.
- What you get
- A review trail that helps explain who did what without exposing credentials or claiming every event is transactionally durable.
How the work progresses
Who uses it
Workspace owners and authorized administrators assigning access and reviewing sensitive activity.
- Locate the supported sensitive activity or accounting workflow.
- Inspect retained actor, state and event context alongside underlying evidence.
- Use the trail for review without treating it as a certification or a promise of universal durable logging.
A concrete example
Illustrative, not customer data.
What still needs judgment
Controls support a customer's security program but do not by themselves guarantee compliance. SCIM and service-account public pages are intentionally omitted because general availability is unconfirmed.
AI cannot grant permissions, enforce identity policy, erase audit history, disclose credentials, or bypass security controls.
Available workflows depend on your plan, permission scope, configuration and supported data. Compare plans before choosing.
Before you use auditability
Can I explore this before connecting company data?
The public demo is a fixed, read-only sample company. It illustrates supported product areas without creating an account or accessing customer data; it is not proof that every configured workflow is available in the tour.
What should I verify before relying on an output?
Confirm scope, source coverage and timing. For this capability, review supported scoped audit events, actor and workflow context, and immutable accounting outcomes. An operating status or AI explanation does not replace the required review of accounting evidence.
Does an explanation automatically authorize a financial action?
No. AI cannot grant permissions, enforce identity policy, erase audit history, disclose credentials, or bypass security controls.
Continue the workflow
See the work in context.
Explore a read-only sample company, or start with your own supported data.