Configure a Rovo agent's identity
Rovo agents can find information and perform tasks across your Atlassian and connected apps. You can control what Rovo agents access using organization-wide settings or specific permissions set by the person who created the agent. More about managing agents in your organization
When you build an agent, you decide which identity the agent will use — either a User's account or the Agent's account. If the agent adopts a user’s account, than the agent can access whatever that user can.
If an agent is configured to use its own account, organization admins decide which apps the agent can access. Space admins and end users then decide which spaces or pages the agent is permitted to access.
Understand Rovo agent accounts
Choose your agent’s set up
You can decide which account the agent will use when you first create it. You can switch accounts if the agent’s core tasks change, keeping in mind any knock-on effect that might have, particularly for your automation flows.
There are two options, each with optimal use cases.
Access type | Description | When to use |
|---|---|---|
User’s account | The agent adopts the identity of the user who’s interacting with, or automating, the agent. It will have all the same permissions as that user. | Great for chat, ad-hoc tasks, or personal assistance. |
Agent’s account | Sets up the agent with its own account, managed by the organization, space, or app admins (just like a user). | Best for agents in automations. It allows the agent to run in automations, without relying on a user’s access. |
To choose which permissions an agent uses:
If you’re not already there, navigate to Studio using the app switcher ().
Select the agent you’d like to configure.
In the agent's settings, select Access and identity from the sidebar.
From the User’s account or Agent’s account card, select See details to review each account.
When you feel confident with your choice, Select this account to set your agent’s account.
Imagine you want every new Jira work item automatically triaged.
Using Agent’s account, the agent acts under its own identity, with only the permissions granted to it by you, admins and other users. When an event triggers, and the agent runs, any changes will appear under the agent's name making it easier to track in audit logs.
If you were to change the agent to have a User’s account the agent will use the permissions of whoever sets up the trigger or automation. This means that changes will be logged as being performed by a user (or users) not the agent.
Whenever you’re planning to adjust your agent’s identity, you’ll be offered all the essential details so you can make an informed decision.
View the apps an agent can access
Agents with the Agent’s account have their app access defined by organization admins, just like users. They decide which Atlassian apps the agent can (or can’t) access.
These apps are listed in the Access section of your agent’s settings. A cross () indicates that the agent does not have access to that app. To update what apps the agent can access, get in touch with your admin.
Organization admins can manage agents in Atlassian Administration
Grant access to spaces and pages
App access is the first layer. Your agent will still need to be granted access to spaces and pages you want it to work with.
This may happen automatically depending on the way your admin sets up your Atlassian apps. Otherwise, you or the space owner might need to grant the agent access to the specific content.
You can test your agent first by asking it to complete a task in the space where you want it to work.
Was this helpful?