Agents act within delegated reach.
A handoff retains the person behind the task and cannot enlarge their authority.
Identity & Security
Authority that holds
from the first request
to the final change.
Know who is acting, for whom, and under whose authority, at every step of the work.
Authority travels with the work through data, models, approvals and waits, and is checked again right before a governed change reaches your systems. If it has lapsed, that action cannot run.
Use enterprise SSO, Frozion’s built-in identity provider with FIDO2 passkeys, or both.
FROZIONExecution FabricGoverned from request to outcome
Business operationSettle invoice INV-1042Tenant A · Accounts payable · $12,240
- ap-user-42Asked for it · their own authorityRequest
- invoice-agent-7Acting for them · limited scopePrepare
- controller-17Approves · own authority · passkeyApprove
Checked again right before the changeCurrent authority + policy + exact approved proposal
Continuous AuthorityPeople and agents, each with their own identityRight tenant, right reasonDelegation never widens authorityPasskey proof at the moment it mattersStop or revoke at any time
Continuous authority on every adoption path
Govern existing agents
Connected tool calls retain who asked and are checked before they run.
Grow tools into workflows
Authority is checked at governed steps and again after long waits.
Build native agents
Agents you build get their own identity. Stop further governed actions or revoke resource access.
Build systems of engagement
Employees, customers, vendors and partners sign in through SSO, Frozion’s built-in identity with passkeys, or both.
The problem this solves
Signing in is not permission to do everything that follows.
A login identifies the person. Frozion checks whether the person, agent or reviewer still has authority for the action being requested, even after a handoff or a long wait.
Current authority decides the next action.
Revocation, a changed proposal or missing passkey assurance blocks the action that no longer qualifies.
Stop further actions. Keep the record.
Use the kill switch to stop an agent’s further governed actions, or revoke its access to specific resources.
01 / Continuous Authority
Sign-in is where authority starts,
not where it ends.
Frozion knows who is acting, for whom, and whether they still may.
The person who asked, the agent acting for them and the reviewer each keep their own identity and authority. Frozion checks the next governed operation against current permissions, policy and the exact approval.
Follow one invoice
Authority pathEX-1042 · Invoice settlement
Before information enters the decision
Only permitted data reaches the decision.
Tenant, purpose, business scope and source permissions determine which records and facts the agent may use.
See precise reach →What this person may do here
How precise reach works →Roles set what someone can do. Business scope sets where, down to the record.
02 / Right before the change
Same invoice.
Different authority. Different result.
A capable agent with a valid credential still cannot act without current authority. Try it.
Change one condition to see whether the invoice request passes its authority, policy, passkey and exact-approval checks. This example never calls your ERP.
Current action gateNot checked yet
Pick a condition to see what happens.
The example checks authority locally, without calling an external system.
Required next step
Evaluate the current selection.
Boundary evidence
No evaluation recorded for this selection.
Allowed is not the same as done.
An authority check permits the governed request; it does not prove a payment happened. The change is marked confirmed only once the target system confirms it. Missing confirmation remains unresolved.
Controls for every connected agent.
Each agent has its own identity.
The agent stays distinct from the person it acts for. Built-in identity with FIDO2 passkeys and enterprise SSO connect people to the same authority model.
Delegation only narrows.
An agent-to-agent or agent-to-tool handoff cannot enlarge the authority it receives.
Authority is checked before the change.
The current scope, policy and required approval decide whether a governed action may proceed.
Only authorized tools run.
Registered tools execute through Frozion only when the requested operation is permitted.
Revoke access to a resource.
Remove the agent’s permission to particular resources, including for its next governed operation.
Stop further actions.
The kill switch stops an agent’s further governed actions. Completed work stays on the record.
03 / People, assurance & time
Approvers see exactly what they approve.
Only that version can run.
The approval is part of the same record as the work.
The proposal, permitted evidence, policy and exact amount are presented together. Where policy requires it, a FIDO2 passkey step-up confirms the reviewer for that decision.
Review Package · RP-1042-A
Release $12,240 for INV-1042 r5
EvidenceInvoice r5 · PO r2 · receipt r2
Calculated facts2.0% variance · FS-1042-A
Decision contextCP-1042-A · AP policy v4
Authorized reviewercontroller-17 · Tenant A
Required assuranceFIDO2 step-up at approval
Tied toHA-1042-A → exact r5 proposal
One package holds the proposal, permitted evidence, versions, reviewer, passkey proof and decision. Only reviewers with the right scope can open it.
Reviewers approve with their own authority.
They never borrow the agent’s. Their own current scope decides which case they may review and approve.
A passkey at the moment it matters.
Where policy requires it, high-stakes approvals ask for a FIDO2 passkey step-up tied to that one decision.
Change the invoice, and the approval no longer applies.
If r6 becomes $12,960, the r5 approval does not authorize it. The revised proposal needs a new approval; the r5 decision stays on the record.
Across waitsWork can wait.
Work can wait.
Authority is checked again when it resumes.
Who asked, who approved, the exact proposal and the state of the case remain connected across waits and runtime nodes. The next action still needs current authority.
See how work survives waits- 01Review completed.Recorded
The decision is kept, tied to the exact version approved.
- 02Work waits.Retained
Who asked, under what authority, and where the work stands are all kept.
- 03Work resumes.Checked
Expiry, policy changes, revocations and new actors are checked before continuation.
- 04The change is about to run.Enforced
It runs only if authority, required approval and policy all still hold.
- 05Stop it at any time.Stopped
The kill switch stops further governed actions. Revoke removes access to specific resources; completed actions stay on the record.
04 / Shared security foundations
One authority model across
every agent, workflow and app.
Your existing controls stay in charge. Frozion adds what happens between them.
Use your enterprise SSO or Frozion’s built-in identity with FIDO2 passkeys. Source permissions, service IAM, network controls and system-of-record authorization remain part of the boundary.
Only permitted data shapes the decision.
Tenant, purpose, business scope and source permissions determine which records and calculated facts reach the governed workflow. Source references stay connected to the case.
Explore governed data & contextWork runs only where its data is allowed.
Private work stays inside its approved boundary. A model or service receives only the inputs its task allows; an outage cannot widen that permission.
Explore Private & Hybrid AI| What you already run | What Frozion adds |
|---|---|
| Sign-in & assuranceYour SSO, or Frozion’s built-in identity provider with FIDO2 passkeys. | Who is acting at each step, and passkey proof where the decision requires it. |
| Source accessSource permissions and enterprise ACLs. | Only permitted data reaches features and workflows. |
| Service invocationAPI authentication and service IAM. | The person or workload behind the request, delegated scope, purpose and the exact operation stay connected. |
| InfrastructureYour cloud, private, network and on-premises controls. | Approved inputs and model routes remain subject to the application’s rules. |
| Changes to your systemsSystem-of-record authorization and committed state. | Current authority, the exact approved proposal, and the reported outcome stay on the same record. |
| Security & auditYour audit and evidence processes. | A tamper-evident record you can export, with scoped, read-only access for auditors. |
After the actionOne record of the governed work.
One record of the governed work.
Each reader sees what they are allowed to.
Auditors get scoped, read-only access. Nobody sees beyond their permissions.
See six investigation viewsExport the record, or give auditors scoped, read-only access.
The same connected evidence supports review without granting broad access to protected records.
05 / Questions, answered
Identity establishes who.
Authority governs what.
Every person, agent and approval behind an action stays distinct, and on the same record.
Only if you want it to. Use your enterprise SSO, Frozion’s built-in identity provider with FIDO2 passkeys, or both. Customer and partner apps can use the built-in provider, so you do not need a second identity product for them.
No. A credential proves which service is calling. What the agent may actually do is checked separately on each governed call.
Tenants are kept apart first, with separate users, data and evidence. Roles then set what someone can do inside their own tenant. Business scope makes that reach precise, down to the record.
No. Authority is checked again when work resumes and right before a governed change. If it has expired or been revoked, the action cannot proceed under that authority.
The approval no longer applies. It is tied to the exact version approved, so a changed invoice needs a new approval.
Auditors get scoped, read-only access to evidence, so they see what their permissions allow and nothing beyond it. The record can also be exported.
Yes. The kill switch stops an agent’s further actions through Frozion. Revoke removes its access to specific resources. Completed actions stay on the record; neither control reverses work already completed.
The next step is checked against current permissions before it runs. The record keeps what applied before, and the work continues, waits for a new approval or stops according to the current policy.
From sign-in to the final change
Every action, checked against
who is acting, right now.
Bring one high-stakes action. We’ll show who is behind it, what they approved, and what stops it when authority changes.