Identity and Access
Identity is the layer that records who and what can reach the estate, from human accounts to service accounts, keys, and agents. Atlas Bench designs and cleans up that model across Okta and Atlassian Guard, so access can be proven rather than assumed.
Human and non-human identity, SSO, SCIM, least privilege, access reviews, Guard cleanup, Agent SSO readiness.
The problem
Identity is the layer everything else rests on, and it is usually the last one anybody owns. Accounts arrive through acquisitions, contractor onboarding, and tools bought by a single team. Groups get created for a project and outlive it. By the time a directory is connected to the work platform, nobody can say from memory who holds admin, which accounts belong to people who left, or which integrations are authenticating as a human.
That uncertainty does not stay in the identity layer. It surfaces as a failed access review, a migration that cannot map users cleanly, a permission scheme nobody will touch because the blast radius is unknown, and now as agents that need their own identity and inherit whatever the humans already had. Every one of those is cheaper to fix as an identity problem than as the thing it turns into.
identity svc-jira-sync class non-human owner platform engineering source okta, scim provisioned grants jira-admin, confluence-admin decision renew, scope reduced to jira-admin
Recent from the blog on this layer.
Non-Human Identities in Atlassian Cloud: Service Accounts, Tokens, Apps, and Agents
How to govern non-human identities in Atlassian Cloud: service accounts, API tokens, Forge apps, and Rovo agents, each with an owner, scope, and expiry.
September 24, 2026What Is Identity Debt in Atlassian Cloud Migration
Learn what identity debt means for Atlassian cloud migration and how to audit unowned accounts, stale permissions, and legacy access risks.
March 31, 2026Atlassian Guard Has a New Data Security Policy
Learn how Atlassian Guard's new unified data security policy simplifies enterprise-wide protection across Jira and Confluence.
Training
Learn this layer in a class.
Live classes on the official curriculum, taught by the architects who run these platforms, each with a hands-on sandbox of your own.
The other three layers.
One accountable system of work. Every layer is a front door to the rest.
Agents and Automation
Rovo, Agents in Jira, Forge, MCP with Claude and Copilot, agent lifecycle, usage and cost governance.
Governance and Change
Permission architecture, audit and compliance, ITSM and change control, change management, strategic reporting and budgets.
Platform and Migration
Migration of every kind, tool consolidation, licensing, standardization, the system of work.