Skip to main content

​
AtlaSent authorizes consequential actions before they happen.

One authorization model can govern deployments, business-system changes, clinical actions, identity changes, and AI-agent execution. The action is authorized against the organization’s current rules and evidence, and the resulting permit is bound to the exact execution plan. AtlaSent authorizes the specific plan about to run — not the vendor, not the tool, not “deployments in general.” Each surface below is governed by a canonical action that already exists. Adding a new system of record does not add a new action; it adds context and evidence on an existing one. The catalog stays small; the plan drives the policy.

Production Deploy

Gate a CI/CD deployment of code, configuration, or infrastructure behind a signed, single-use permit bound to the exact release.
CANON-000001 · production.deploy

Salesforce Configuration

Gate a permission-set, profile, flow, or config change — deployed as a change set — before it lands in a production org.
CANON-000001 · production.deploy · illustrative scenario

NetSuite Financial Configuration

Gate a role, workflow, or SuiteScript change — packaged as an SDF project — that alters financial controls.
CANON-000001 · production.deploy · illustrative scenario

Clinical Trial Unblinding

Gate planned and emergency unblinding with dual authorization or requester-MFA — an auditable, 21 CFR Part 11-aligned record of who authorized the reveal.
CANON-000018 · trial.unblinding.execute · CANON-000020 · trial.unblinding.emergency

Identity & Access Changes

Gate access grants, privileged-identity grants, and break-glass overrides with verified authority before the change executes.
CANON-000007 · access.grant · CANON-000025 · identity.privileged.grant · CANON-000009 · control.override

Database Schema Changes

Gate a production migration — the schema change that can corrupt or expose data — behind an authorization permit and state snapshot.
CANON-000032 · database.migrate

Infrastructure Changes

Gate a change to cloud or platform infrastructure — the destructive plan, the IAM change, the state operation — at execution time.
CANON-000033 · infrastructure.change

AI Agent Actions

Gate the AI-agent tool calls you route through AtlaSent — verify a real identity, evaluate policy, and permit before the action runs. Fail-closed.
CANON-000026 · agent.tool.invoke

​
One action, many systems of record

Look closely at the first three cards. Production Deploy, Salesforce Configuration, and NetSuite Financial Configuration all resolve to the same canonical action — CANON-000001 · production.deploy. The interception point is identical: execute the authorized change or deployment plan. A Salesforce change set and a NetSuite SDF project are change plans, exactly like a CI/CD release is a change plan. See Change-plan execution for how one action covers them all without claiming that every execution is source-code deployment.

​
How to read the labels

Shipped

A surface with live runtime enforcement. The AI-agent guard ships in the SDK and the MCP server.

Canon

A canonical action defined in AtlaSent’s authorization model. Runtime maturity varies by domain — see each product area for its current state.

Illustrative scenario

A reference design showing how an existing action applies to a system of record. Not production-proven at a customer, and no customer is represented.
Every surface on this page maps to a canonical action that already exists in AtlaSent’s authorization model — no new action was minted to cover any of them. The Salesforce and NetSuite scenarios are illustrative reference designs, not claims of a deployed customer integration.

​
The contract, everywhere

Fail-closed. Offline-verifiable proof. The same six-step contract governs a production deploy, a business-system change plan, a clinical unblinding, an identity change, and an AI-agent tool call. Start with the Runtime flow, or see what a governed change plan looks like end to end in Change-plan execution.