AtlaSent puts an enforceable decision between people, software and AI agents and the production changes and business actions that matter. It refuses what your organization has not authorized, and keeps the decision, the execution and the effect as separate records.
Change the action and it needs approval again.
PeopleSoftwareAI agents
Action Catalog
Software and AI can prepare the work. AtlaSent controls the consequential action at the point it executes.
Actor+Action+Resource+Context+Authority requirements+Evidence→DENYHOLDPERMIT
| Work AI or software can prepare | Consequential action AtlaSent controls | Canon |
|---|---|---|
| Draft an agreement | Sign agreement | Canonical action identity.sign |
| Complete an application | Submit application | Custom action today |
| Find availability | Schedule appointment | Custom action today |
| Draft correspondence | Send message | Canonical action communication.external.send |
| Prepare an order | Place purchase | Canonical action workflow.approve |
| Reconcile an invoice | Pay invoice | Canonical action finance.payment.authorize |
| Prepare a transfer | Move money | Canonical action finance.wire.transfer |
| Analyze a refund | Issue refund | Canonical action finance.payment.authorize |
| Prepare a filing | Submit filing | Nearest canonical action compliance.certify |
| Generate content | Publish externally | Canonical action content.publish |
| Evaluate a user | Grant access | Canonical action access.grant |
| Prepare records | Release data | Canonical action data.export |
| Generate or change code | Deploy production | Canonical action production.deploy |
| Prepare infrastructure change | Change infrastructure | Canonical action infrastructure.change |
| Determine an emergency action | Unblind / override | Canonical action trial.unblinding.emergency control.override |
| Anything else your systems or AI prepare | Custom action | Define your own |
Enterprise products
Deploys, infrastructure and configuration changes run only when the exact change is authorized: the right identities, approvals and separation of duties, bound to the repository, commit and environment. Change the work and it needs a new decision.
Agents can hold credentials and tool access without your organization’s permission to act. AtlaSent gates the consequential tool call, records the agent’s provenance, holds for a person when your rules require one, and refuses when authority cannot be established. We confirm the supported agents, tools and execution paths with your team before activation.
How protection works
An approval decision is not proof the action ran. AtlaSent verifies the permit at the point of execution, and records what happened only when it is actually observed or reported.
Identity is not authority. Approval is not authorization. An allow decision is not proof of execution. Permit verification is not execution success.
Illustrative example
On a connected production-change path, approving one change does not authorize a different one.
A reviewer approves a specific repository, commit and production environment. The permit is bound to that request.
The commit or target changes after review. The original approval does not cover the new request.
The changed request cannot use the original permit. It needs a new decision before execution.
This is an illustrative workflow, not a live customer result. Decision, permit verification, execution and observed effect remain separate records. Protection covers the execution paths that enforce the check.
Enterprise operating layer
Enterprise adds the layer that lets security, platform and risk owners see what is protected, what is not, and why, across teams and systems.
Every protected action in one place: what it protects, the path it runs on, the requirements it enforces and its current state.
Each action and execution path is Complete, Partial, Unknown or Not configured. Unknown stays Unknown. It is never shown as protected.
People, services and AI agents are resolved as distinct identities. Enterprise identity and member administration are confirmed for your environment in the agreement.
Approvals, separation of duties and independent review are required where your rules say, and kept separate from who can administer the rules.
Blockers, gaps and drift are surfaced with the exact repair, so owners can fix protection instead of reading a wall of green checks.
Every decision leaves a signed, hash-linked record you can verify offline. Execution and effects are recorded only when they are actually observed.
Assisted implementation of your first protected action, and support commitments written into the agreement.
AtlaSent Enterprise
Authority Launch proves one consequential action in production: we find the execution path with your team, configure your requirements, prove a refusal and a valid run, and prepare a separately authorized production activation. Then expand into an annual Enterprise agreement.
Other consequential actions
Admin grants, new roles and break-glass access, checked against who may approve them before they take effect.
Exports of customer, patient or audience data to another system or party, held until the right person authorizes the release.
Payments, journal entries and close certification, bound to the amount, payee and entity that were authorized.
Batch release, unblinding and validated-system change, with evidence a reviewer can verify independently.
Your systems call AtlaSent before the action. AtlaSent does not replace your identity provider, pipeline or export tool.
For developers
The agent guard and MCP Gate block risky actions on your machine with no account. The TypeScript and Python SDKs, the REST API, the MCP server and the GitHub Action put the same checks in your own code and pipelines. Self-service cloud plans are separate from Enterprise.
Implementation, advisory, channel and technology partners deliver AtlaSent inside the security, technology, finance and AI programs they already run.