Bring trusted identities from your existing provider or use AgenticDome-issued agent identities. Connect the caller, deployment and delegated authority to the action being evaluated.
Identity establishes the caller. Action policy determines what that caller may do in this context.
Use an existing provider such as Microsoft Entra ID or Okta, or a supported workload identity. Your security team configures trust; applications pass the appropriate caller and delegated-user tokens.
Your provider continues to authenticate the principal. AgenticDome verifies the supplied identity and applies it to action policy.
Approve a deployment and bind it to its assigned runtime. Once the deployment proves its enrollment, AgenticDome issues short-lived agent identities for gateway and supported SDK use.
Manage deployments, agent identities, credential rotation and revocation in the Identity workspace.
Approve which deployments may obtain agent identities and keep them bound to the intended runtime.
Review agent identities, runtime instances and recorded caller evidence across the tenant.
Scope authority passed between participating agents. Rotate credentials or revoke deployments while retaining their history.
Explore a local action-security example, plan your approach with Abi or bring your environment to a deployment review.