Least-Privilege Architecture
Keep roles simple.
Make authority precise.
People and agents reach only the work that is theirs: the right region, the right record, for the right reason.
You keep a short list of roles. Frozion adds business scope to each one and holds that boundary at governed steps, from the data an agent reads to the change it makes.
Supplier account-change reviewACME-204 / US-01GlobalCo · account-change verification
Shared roleSupplier Account Reviewer
Reviewer A
North America
Covers US-01
Sees this caseReviewer B
EMEA
Covers DE-01
Does not see this caseRole + tenant + business scope
+ resource + purpose + current conditions
Precise reach at every stepTenants never see each other’s dataRoles plus conditions, not more rolesScope in your business termsAccess down to the record
Precise reach on every adoption path
Govern existing agents
Your agents act only within the business scope you gave them, call by call.
Grow tools into workflows
Scope travels with the work. Delegation cannot give the next step more reach.
Build native agents
Agents you build get their own precise authority, never a service account’s broad access.
Build systems of engagement
Employees, customers, vendors and partners see only the cases their current scope permits.
01 / Stable roles. Specific business authority.
One role.
Every region, product and entity.
No new role for every portfolio, country and classification. Roles stay few; scope does the precise work.
Roles define the kind of work. Conditions and business scope determine where that role applies, for which purpose, and to which record.
Authorization dimensionThe question it answersExample
Tenant & legal entity
Which organizational boundary applies?
GlobalCo / US-01Role / RBAC
What kind of work may this actor perform?
Supplier account reviewTaxonomy scope
Which business branch is in scope?
Procurement / North AmericaResource & action
What exact object and operation are authorized?
Review ACME-204 / proposal r3Purpose
Why may this information or capability be used?
Account-change verificationAttributes / ABAC
What conditions must hold now?
Classification, assurance, state, timeGoverned enterprise meaning
Scope uses your business terms, owned and versioned, not free-text tags.
A name can change, and a region can move or split. Owned, versioned business terms keep assignments tied to the meaning you intended.
Each assignment makes what is included and excluded explicit. A familiar label alone never grants access.
North America
US-01Included
CA-01Included
MX-01Explicitly excluded
Covers: US and Canada.
A new country needs its own scope decision before this assignment includes it.
Region is one check. Every other condition still applies.
A record can match the region and still be restricted by legal entity, classification, purpose or an explicit denial. One matching condition does not clear the rest.
02 / The same role is only the starting point
Same role.
Only the right reviewer sees the case.
Pick a reviewer and a condition, and see who gets the case and why.
The same role covers different business assignments. Record, purpose and current permission decide access; approval and writeback remain separate governed actions.
Same-role review example
Try it
ACME-204 / US-01
Effective authorization
Not evaluatedReady to resolve
Pick a reviewer and a condition. Sharing a role is never enough on its own.
Next permitted step
The reviewer sees the case only after their assignment, the exact record and the purpose all check out.
Scope evidence
The record shows which assignment, taxonomy version, record revision and conditions decided it.
The same ID in another tenant is a different record.
ACME-204 in GlobalCo is not ACME-204 in another tenant. Trusted tenant and source records determine access; a caller-provided name cannot grant it.
03 / From the data read to the change made
Agents see only permitted records.
Their actions stay within scope.
Scope is applied before query results reach the agent.
Roles, business scope and source permissions constrain the inputs and actions of the governed task. Delegation cannot widen that reach, and access to evidence remains subject to the reader’s own permissions.
Only allowed records reach the agent.
Query results are scoped before the agent sees them. A matching role never overrides the tenant, record or purpose check.
Calculated facts keep their scope.
Features retain the scope and source references of the data they came from. Reuse follows the same permission and freshness requirements.
Delegating never widens reach.
An agent or governed step that receives delegated work gets the same scope or less. A shared runtime does not add permission.
Approval covers this record, this action.
Access to a tool never means access to everything behind it. The exact resource, action, purpose and current authority still decide.
Evidence respects who is reading.
Reviewers and auditors inspect evidence only within their own current permissions. Connected records do not grant access to unrelated protected data.
Less over-permissioning.
Each task gets the functions, records and actions it needs, nothing more.
Less role sprawl.
When someone changes region or portfolio, you change their assignment, not their role.
Faster investigations.
For a governed change, see which assignment, policy and approval allowed it.
04 / When someone’s scope changes
A reassignment is checked
before the very next step.
Work in progress is checked again before it continues, and the record keeps what applied before.
Work continues, narrows, goes back for approval or stops, whichever the new scope allows.
How continuous authority works →Your existing controls stay in charge
Frozion adds to your access controls; it does not replace them.
Your identity providers, cloud IAM, source ACLs and database row-level security keep their responsibilities. Frozion adds the request’s purpose, workflow step and current business scope to the governed operation.
Tenants share infrastructure, never data.
Within your dedicated Frozion instance, each tenant keeps its own users, data and evidence. Sharing infrastructure does not grant one tenant access to another’s records.
Explore Private & Hybrid AI05 / Questions, answered
The right function.
The right business scope.
Roles, conditions and business scope work together on every governed action.
No. Keep your roles. Frozion adds conditions and business scope on top, so you need fewer roles, not a new model.
A tag can be mistyped or drift. Taxonomy scope uses your business terms with an owner and a version, so “North America” means the same thing wherever that definition is used. Changes to it stay on the record.
They stay in charge at the source. Frozion adds the purpose of the request, the step in the workflow and the governed actions an agent takes with the result.
No. Each governed call is checked against the exact record and action. Access to a tool never means access to everything behind it.
The next step is checked against current permissions before it runs. See continuous authority.
No. It limits the damage a manipulated request can do through governed actions: the agent stays within its permitted scope, and each action is still checked and recorded.
Least privilege, in business terms
Keep roles simple.
Give every agent exactly the reach it needs.
Bring one application. We’ll show its roles, the business scope each one needs, and the actions those checks guard.