nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Subject: Rovo Agent Unable to Retrieve Full Atlassian users

Fatima AALLA

I am testing a Rovo Agent intended to perform user account reviews and user recertification against our Atlassian Organization.

My objective is to build an automated User Recertification Agent that:

* Retrieves all users from the Atlassian Organization or from specific groups (such as "jira-servicedesk-users").
* Retrieves all ACTIVE human users.
* Excludes system, application, bot, service, and automation accounts.
* Reviews user activity.
* Identifies inactive users based on a configurable threshold (currently 180 days).
* Produces a recertification report for access reviews and license optimization.

I am an Organization Admin, and my expectation is that the agent should be able to retrieve all managed users and group members from the Atlassian Directory.

However, the agent appears to be limited to approximately 50 returned users and cannot perform pagination, I tried to give the agent a rest API that fetchs the group members but The agent repeatedly responds with messages similar to:

"The available tools do not provide the functionality to specify startAt, maxResults, or check for isLast for pagination."

and

"The jira_atlassian_user_search_by_query tool returned a maximum of 50 users and does not support pagination."

Questions:

1. Is Rovo currently capable of calling Atlassian Administration REST APIs such as:

GET /admin/v1/orgs/{orgId}/directory/users

GET /admin/v1/orgs/{orgId}/directory/groups/{groupId}/members

2. If I am an Organization Admin, should Rovo inherit my admin permissions when executing agent actions?

3. Does the built-in jira_atlassian_user_search_by_query tool have a hard limit of 50 results?

4. Does this tool expose any pagination mechanism (startAt, cursor, nextPageToken, offset, etc.) that Rovo can use?

5. Is there currently any supported method for a Rovo Agent to retrieve the complete membership of a large Atlassian group?

6. If built-in Rovo tools cannot perform this operation, is the recommended approach to create a Forge Action or custom Action that calls the Atlassian Admin APIs directly?

7. Are there any documented limitations preventing Rovo Agents from accessing Atlassian Administration APIs even when the user executing the agent is an Organization Admin?

8. Is there a supported way for a Rovo Agent to retrieve Last Seen / Last Active information for all users in the organization so that inactive accounts (e.g., users inactive for 180+ days) can be identified automatically?

9. Is user recertification and access review considered a supported use case for Rovo Agents, and if so, what is the recommended architecture?

Agent Prompt Used:

You are an Atlassian Jira Service Management Account Review Agent.

TARGET DATASET

Retrieve users who are members of the group "jira-servicedesk-users".

Requirements:

* Retrieve all group members.
* Use pagination until all pages are processed.
* Never analyze only the first page.
* Include only ACTIVE human users.
* Exclude System, App, Bot, Service, and Automation accounts.
* Report total members found.
* Report total ACTIVE members.
* Provide Display Name, Email Address, Account Status, Last Seen, and Status.
* Report excluded accounts and reasons for exclusion.
* Never generate a report from a partial dataset.

Expected Behavior:

The agent should retrieve the complete membership of the group and all available pages before generating a report. For user recertification purposes, the agent should also be able to identify users that have not accessed Atlassian products for 180 days or more.

Observed Behavior:

The agent only retrieves approximately 50 users and reports that pagination is unavailable through the tools exposed to the agent.

Could you please clarify whether this is an expected product limitation, a permissions issue, or whether additional configuration is required?

Thank you.

Accepted answers

Arkadiusz Wroblewski

@Fatima AALLA

I'm repeating it everywhere. Answers from AI cannot be treated as deterministic. They always must be revalidated.

Some custom forge-based app should be able to handle that. Output from basic Rovo prompts will respect your Admin scopes, but at the other hand, you can't rely on it to expose all endpoints related to your permissions and call them. And from a security standpoint, it makes sense.

About pagination and limited rate output around 50 is pretty common. I've seen a couple of QA about that.

You should keep an eye on that, because Rovo is evolving on a daily basis, so what wasn't possible last month could be possible next.

Cheers,

Arek 🤠

All comments

HEMANT SAINI

Hi @Fatima AALLA

You are hitting current Rovo platform limits. I ran into the same thing building an access review agent last month.

Short answers to your questions:

1. Can Rovo call Atlassian Administration REST APIs
Not directly today. Rovo Agents can only use the tools Atlassian exposes to them. The Admin APIs like /admin/v1/orgs/{orgId}/directory/users are not exposed as built-in actions yet. You cannot make arbitrary REST calls from a standard Rovo Agent.

2. Does Rovo inherit my Organization Admin permissions
No. The agent runs with its own service identity and only gets the scopes for the tools Atlassian gives it. Even if you are an Org Admin, the agent does not inherit those rights for Admin APIs. It only sees what the built-in user search tools can see.

3. Is jira_atlassian_user_search_by_query limited to 50
Yes. That tool has a hard cap of 50 results and no pagination parameters exposed to the agent. This is a known limit. The message you saw about startAt and maxResults is accurate.

4. Does the tool expose any pagination mechanism
No. There is no cursor, offset, or nextPageToken available to Rovo from that tool right now.

5. Any supported method to get complete membership of a large group
Not with built-in Rovo tools today. You will only get the first 50 users. For groups larger than that, the dataset will always be partial.

6. Is Forge Action or custom Action the recommended approach
Yes. This is the current recommended path. Build a Forge app with an Action that calls the Admin APIs using asApp or asUser with proper scopes. Then expose that Action to your Rovo Agent. Your Forge app can handle pagination and return the full list to the agent for analysis. You will need admin consent for the org.read scope.

7. Any documented limitations for Rovo accessing Admin APIs
Yes. The Rovo docs state that agents can only access product data through supported actions. Admin directory and audit logs are not exposed yet. Organization Admin role does not override this.

8. Can Rovo get Last Seen or Last Active for all users
Not today. The built-in user tools do not return last activity timestamps. The Admin API /audit endpoint has some login events, but again Rovo cannot call it directly. You would need a Forge Action to pull audit logs, calculate the 180 day threshold, and pass the result back.

9. Is user recertification a supported use case and recommended architecture
Atlassian has mentioned access review as a target use case for Rovo, but the native tools are not there yet. Recommended architecture today is:
Step 1: Forge Action that calls /admin/v1/orgs/{orgId}/directory/groups/{groupId}/members with pagination
Step 2: Same Action calls audit or login data to compute last active date
Step 3: Action returns a clean JSON list to Rovo
Step 4: Rovo Agent does the reasoning, flags inactive users, and generates the report or Jira tickets

Observed behavior is expected product limitation, not a permissions issue on your side.

You can track this gap under the Forge and Rovo roadmap. Search for Rovo Admin API access and Rovo pagination for user search in the Atlassian Developer Community. Add your use case. More votes will push it up.

For now, Forge Action is the only way to get full group membership and last active data into Rovo.

Fatima AALLA

hello @HEMANT SAINI

thank you for your support,

yes please provide detailed steps as I'm new to forge

Thank you in advance

Regards,

Arkadiusz Wroblewski

@Fatima AALLA

I'm repeating it everywhere. Answers from AI cannot be treated as deterministic. They always must be revalidated.

About pagination and limited rate output around 50 is pretty common. I've seen a couple of QA about that.

You should keep an eye on that, because Rovo is evolving on a daily basis, so what wasn't possible last month could be possible next.

Cheers,

Arek 🤠

HEMANT SAINI

Hi @Fatima AALLA

Happy to help! Since you’re new to Forge, here’s the full path to get your Rovo agent pulling complete group membership plus last active data. This is the setup we use for access reviews:

Goal
Build a Forge Action that Rovo can call. The Action uses Admin APIs with pagination. It returns the full user list to your agent for analysis.

Step 1: Set up your Forge app

Install prerequisites: Node.js 18 or higher, then run this command: npm install -g @forge/cli
Log in: run forge login and authorize with your Atlassian account
Create app: run forge create, choose Rovo agent action template, name it access-review-action
Get your Org ID: Go to admin dot atlassian dot com, Settings, Details, copy your Organization ID. You will need it.
Step 2: Add permissions to manifest dot yml
Replace your manifest dot yml file with the text below. The key scopes are read colon organization-user and read colon audit-log.

Paste this into manifest dot yml:

modules:
rovo action:
- key: get-group-members-full
name: Get Full Group Membership
description: Pulls all members of a group with last active data
function: resolver
inputs:
groupId:
title: Group ID
type: string
description: The groupId from admin dot atlassian dot com Directory Groups
actionVerb: GET
function:
- key: resolver
handler: index dot handler

permissions:
scopes:
- read:organization-user
- read:audit-log
external:
fetch:
backend:
- api dot atlassian dot com
app:
id: ari:cloud:ecosystem::app/your-app-id

Step 3: Write the Action code in src slash index dot js
This handles pagination and calls 2 Admin APIs. Install deps first: npm install @forge/api @forge/resolver

Paste this into src slash index dot js:

import Resolver from '@forge/resolver';
import api, { route } from '@forge/api';

const resolver = new Resolver();

resolver.define('get-group-members-full', async ({ payload }) => {
const { groupId } = payload;
const orgId = 'YOUR_ORG_ID'; // Replace this
let allUsers = [];
let cursor = null;

// 1. Paginate through all group members
do {
const query = cursor? '?cursor=' + cursor : '';
const res = await api.asApp().requestAtlassian(
route/admin/v1/orgs/${orgId}/directory/groups/${groupId}/members${query}
);
const data = await res.json();
allUsers = allUsers.concat(data.data);
cursor = data.links && data.links.next? new URL(data.links.next).searchParams.get('cursor') : null;
} while (cursor);

// 2. Get last login for each user from audit log - 180 days back
const sixMonthsAgo = new Date();
sixMonthsAgo.setDate(sixMonthsAgo.getDate() - 180);
const fromDate = sixMonthsAgo.toISOString();

return {
accountId: user.account_id,
email: user.email,
name: user.name,
lastLogin: lastLogin,
inactive180Days: isInactive
};
})
);

return { users: usersWithActivity, total: usersWithActivity.length };
});

export const handler = resolver.getDefinitions();

Important: Replace YOUR_ORG_ID with your actual Org ID.

Step 4: Deploy and install to your site

Deploy: run forge deploy
Install: run forge install, choose your site, product Confluence or Jira, allow asApp permissions
Admin consent: An Org Admin must go to admin dot atlassian dot com, Apps, your app, Grant access. This approves org dot read scope.
Step 5: Connect it to Rovo

Go to Rovo Studio, Your Agent, Actions, Add action
Select Get Full Group Membership from your Forge app
Prompt your agent: Use get-group-members-full with groupId XYZ. Then list all users where inactive180Days is true and create a Jira ticket for each to review access.
How to get the Group ID
Go to admin dot atlassian dot com, Directory, Groups, click the group, copy the ID from the URL: it looks like.../groups/this-is-the-groupId

Limits to know

Rate limits: Admin APIs are about 100 requests per minute. The code above does 1 call per user for audit logs. For 500 users, add delays or batch.
Audit log retention: Atlassian only keeps 180 days of login events. Anything older returns null.
App install: Must be installed by an Org Admin the first time.
The biggest gotcha is usually the Org Admin consent in Step 4. If you are not an Org Admin, loop one in.

Once this is working, your agent can finally see all 500 plus users instead of just 50.

Regards,
Hemant

Dr Valeri Colon (Connect Centric)

@Fatima AALLA Based on what you’ve tested, this looks like a limitation of the user-search tool currently exposed to your Rovo agent, not your Org Admin permissions. If that tool returns 50 users and exposes no cursor/pagination parameters, prompting the agent to “retrieve all users” can’t overcome it. For a recertification process, I’d retrieve the authoritative directory/activity data outside the agent using Atlassian’s supported Admin APIs, handle pagination there, then give Rovo the resulting dataset or summary for analysis. I wouldn’t use Rovo alone as the system of record for an access review.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management

rovo-atlassian-intelligence