Recent posts
Non-human identities in Atlassian Cloud, explained
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.
October 1, 2026How to choose an Atlassian partner for a Jira migration
How to choose an Atlassian Solution Partner for a Jira migration to Cloud: what to verify, eight questions to ask, red flags, and a shortlist scorecard.
September 30, 2026The 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 24, 2026What identity debt means for an Atlassian migration
Identity debt is the access nobody owns: unowned accounts, stale permissions, and legacy groups. Here is how it surfaces in an Atlassian migration.
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.
September 19, 2026What Rovo agent governance means in Atlassian Cloud
Rovo agent governance in Atlassian Cloud: the permission model agents run under, the admin controls that limit them, and who answers for each agent.
April 16, 2026New Work Types in Jira Business Spaces
Learn how Jira's new work type hierarchy in business spaces gives non-technical teams better structure, and control over their work.
April 16, 2026Web Search in Rovo Agents: What It Is and How to Use It
See how web search in Rovo Agents works, how to set it up, and how teams are using it to bring live web context into their workflows.
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.
February 25, 2026Connect Third-Party Data Sources in Atlassian Analytics
Learn how to connect third-party data sources to Atlassian Analytics for richer, more complete business insights.
February 20, 2026Best Practices for Writing Pull Requests on Bitbucket
Learn the best practices for writing better pull requests on Bitbucket Cloud and how its built-in features help teams and ship cleaner code.
Recent resources
Atlassian usage-based pricing on December 3: what changes and what to set first
On December 3, 2026, Atlassian starts billing usage above your included monthly allowances for most meters, including Rovo credits and Automation steps, as a usage layer on top of your existing subscription. Allowances pool across your organization and refresh monthly, and when extra usage is off or a limit is reached, only that meter pauses. Before December 3, check each meter's extra usage setting in Atlassian Administration, set a monthly limit, and name an owner, because Atlassian's own pages describe the default differently.
guideHow to control which MCP clients and agents reach Jira and Confluence
Control MCP access in Atlassian Administration, under Connectors, then Atlassian MCP server: allow only the client domains you approve, keep API token authentication off unless a named pipeline needs it, and set Read, Write, and Search permissions per app. Every connection still acts as a person or an account with that account's existing Jira and Confluence permissions, so give each one a named owner, minimum scope, an expiring credential, and a review date. The audit log records every MCP tool call with the tool, the action, and the user.
guideService accounts vs agent identities in Atlassian Cloud: which to use and who owns each
Use an Atlassian service account when a script or integration calls Jira or Confluence on its own, and give a Rovo agent its own Agent's account when it runs in automation with no person present. Agents that people chat with should use that person's permissions, and every non-human identity needs a named human owner, a written scope, a credential or access grant with a review date, and a known off switch.
Training
Lessons to watch now
-
Free lesson19 min video10 question quiz
Build a Focus and Talent report with Visual SQL
Atlassian Analytics essentials, with Riley Venable Watch it now -
Free lesson14 min video5 question quiz
Find the automation rules eating your step allowance
Jira automation essentials, with Riley Venable Watch it now