Agents and Automation
Agents are the layer arriving fastest and owned least, from Rovo and Agents in Jira to Forge and MCP connections. Atlas Bench gives them an identity, a scope, and a change record, so an agent is a governed participant rather than an account nobody owns.
Rovo, Agents in Jira, Forge, MCP with Claude and Copilot, agent lifecycle, usage and cost governance.
The problem
Agents are being adopted the way tools always are, one team at a time, ahead of any decision about who owns them. An agent gets access because a person granted it, runs against a budget nobody is tracking, and produces work that enters the same queues as human work with no way to tell the difference afterwards.
The layer is new, the failure mode is not. It is the same shape as unmanaged integrations and unmanaged accounts, arriving faster and with more autonomy. What makes it tractable is that the three layers underneath already answer most of it. An agent needs an identity, a platform to act in, and a change record. Where those exist, an agent is a governed participant. Where they do not, it is another account nobody owns.
The Atlas Bench team provided valuable insights and resources that accelerated our Forge development. Their expertise helped us build custom solutions faster and engage more deeply with the Atlassian ecosystem.
Jason Mueller
Sr. Atlassian Systems Engineer
agent release-notes-drafter identity own account, scim provisioned acts in jira, confluence scope read all, write to one space budget owned by platform engineering, capped record every action attributed and retained with the change
Recent from the blog on this layer.
The complete guide to agent readiness in Atlassian Cloud
Agent readiness for Atlassian Cloud: the five checks to run before you switch on Rovo agents, from identities and permissions to the off switch.
September 28, 2026How to review Rovo agent access in Jira and Confluence
A step-by-step access review for Rovo agents in Jira and Confluence: who can create them, who can use them, what they can change, and what gets logged.
September 21, 2026Rovo agent governance in Atlassian Cloud: a 2026 guide
How to govern Rovo agents in Atlassian Cloud with identity controls, Guard policies, workflow guardrails, and audit trails, so each agent has an owner.
Training
Learn it live or on demand.
Free video lessons you can take today, and live classes with a hands-on sandbox of your own, taught by the architects who run these platforms.
-
Free lesson14 min video5 question quiz
Find the automation rules eating your step allowance
Jira automation essentials, with Riley Venable Watch it now -
Intermediate2 h 50 min
Automate work in Jira
Jira, Jira Service Management Dates on request -
Beginner5 h 30 min
Onboard to Rovo: Search and chat with AI
Rovo Dates on request -
Beginner3 h 15 min
Onboard to Rovo: Create AI agents and automation
Rovo Dates on request
The other three layers.
One accountable system of work. Every layer is a front door to the rest.
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.
Identity and Access
Human and non-human identity, SSO, SCIM, least privilege, access reviews, Guard cleanup, Agent SSO readiness.