Who can use Advanced User Manager

Who can use Advanced User Manager

Advanced User Manager is an administration tool. Every screen in the console and every action it performs is gated on Jira administrator permission, and two specific actions need a second, separate permission on top of that. This page explains which permission covers what, and — just as importantly — what the app looks like when you do not have one, because in most cases it does not show an error.

The baseline: Jira administrator

Prerequisite for everything. You need the Jira Administer Jira global permission. The app checks it on the server for every request, using your own account — not the app's. If the check fails, the request stops there and nothing is read or written.

This applies to all of it: Overview, Jira users, External users, Activity & last seen, User properties, Automation and Custom fields — and to every action inside them, including bulk-create, activate/deactivate, CSV import, CSV export, property edits and adding or deleting external users.

To check whether you have it, open Jira Settings → System → Global permissions and look for a group you belong to under Administer Jira. Product access alone is not enough, and neither is being a project administrator.

What it looks like when you do not have it

This is the single most common "the app is broken" report, and it is almost never a bug. When the permission check fails, the app returns an empty result rather than an error, so the console renders as if your site simply had no data. Treat all of the following as symptoms of a missing permission:

Where

What a non-admin sees

Where

What a non-admin sees

Overview

Stat cards showing zero, an empty Recent activity list and empty Last-seen coverage.

Jira users / External users

An empty table and count badges of 0 in the sidebar — the same appearance as a site with no users.

User properties

No property definitions listed, even though they exist. Property columns and the Set properties drawer therefore look empty too.

Activity & last seen

An empty activity log.

Group pickers

No group suggestions when you type.

Bulk actions

The action appears to run and then changes nothing. Activate/deactivate and adding Service Management customers are the exceptions: those two report a permission message explicitly.

Before raising a support request about missing or empty data, confirm your own account holds Administer Jira. A useful cross-check: ask a known Jira administrator to open the same screen. If it is populated for them, the permission is the cause.

Two other things produce an empty Jira users table and are worth ruling out at the same time: the status segmented control defaults to Active, so inactive accounts are hidden until you switch it to Inactive or All; and the Search by name or email box may still hold a filter.

Where Jira administrator is not enough

Two operations call Atlassian services that sit outside Jira and enforce their own permissions. Being a Jira administrator does not grant either of them.

Activate and deactivate — organization admin

Changing an account's activation goes to the Atlassian user management API, which answers to your organization, not to your Jira site. It requires:

  1. An organization API key, created at admin.atlassian.com → Settings → API keys by an organization admin. It must be created under API keys without scopes — the user management API is not covered by any scope, so a scoped key is refused no matter which boxes you tick.

  2. The target account to be a managed account of the organization that owns that key: its email domain verified and the account claimed, so it appears under admin.atlassian.com → Directory → Managed accounts. Accounts on consumer domains such as gmail.com or outlook.com can never be managed.

The app pre-checks every selected account before it runs and shows an amber panel listing the ones it cannot change, so you find out before the bulk run rather than after it. Common refusals:

What you see

What it means

What you see

What it means

403 "Caller must be a verified org admin of targeted account"

The account is not a managed account of the organization that owns your key. If you belong to more than one organization, check that the key comes from the one that claimed the account.

403 on every account

The key was probably created with scopes. Recreate it under API keys without scopes.

401

A personal API token from id.atlassian.com was entered instead of an organization API key.

Provisioned via SCIM or Google Workspace

The account is synced from your identity provider and must be deactivated there. No Atlassian API key can change it from this side.

The organization API key is stored by the app (in Forge storage) and reused for later activate/deactivate runs. It is not discarded after use. Treat it like any other long-lived credential: rotate it at admin.atlassian.com if it is ever exposed or if the person who created it leaves.

Service Management customers — service desk administrator

Both Add as customer and the Also revoke their Service Management portal access option on deletion call Jira Service Management, which requires the caller to be a service desk administrator on the project concerned. The app makes these calls as you, the signed-in administrator, so your project role decides the outcome.

If Service Management answers 403, add yourself to the Administrators role under Project settings → People on that service desk and retry — or make the change by hand under Project settings → Customers.

Two limits here are about the product, not about permission, and no permission level removes them:

  • Customers cannot be removed from a service desk with open access; Atlassian refuses with 400. On such a project the customer list does not control access anyway. To restrict it, set Project settings → Channels & self-service to Customers added by agents and admins.

  • Nothing in the app deletes an Atlassian account — no API can. Removed customers still appear in the site-wide customer list and on requests they already raised, and customer organization membership is a separate access path that revoking portal access does not touch. Only an organization admin can delete the account, by hand.

Bulk-creating Jira users uses your own credentials

Bulk-create runs against your Jira site using a personal Atlassian API token plus the email address of the account that owns it, created at id.atlassian.com → Security → API tokens. The accounts are therefore created as that person, and that person must be a Jira administrator. The token is entered once in the CSV import dialog and stored for reuse.

These are two different credentials and they are not interchangeable: the personal API token (id.atlassian.com) is only for bulk-creating Jira users; the organization API key (admin.atlassian.com) is only for activate/deactivate. Both are stored by the app and reused.

What non-admins can still use

The workflow and custom field extensions are configured by administrators but used by ordinary Jira users, and they behave differently:

  • The (AUM) Copy User Property post function runs with the app's own identity, so it works on a transition performed by any user — the person moving the issue does not need administrator permission.

  • The workflow condition and validator evaluate the property values of the user attempting the transition, again without requiring that user to be an administrator.

  • The Single and Multi External User Picker fields are the exception to watch. The list of external users they offer is read through the same administrator-gated call as the console, so a non-admin editing the issue sees the picker load with no external users to choose from. If reporters need to select external users themselves, plan around this rather than treating the empty picker as a defect.

Quick reference

Action

Jira administrator

Additional permission

Action

Jira administrator

Additional permission

View any console screen

Required

—

Create, rename, delete user properties

Required

—

Set property values, import last-seen CSV, export selection to CSV

Required

—

Bulk group operations

Required

—

Bulk-create Jira users via CSV

Required

Personal Atlassian API token belonging to a Jira administrator

Activate / deactivate accounts

Required

Organization API key without scopes, and the account must be a managed account

Add as customer / revoke portal access

Required

Service desk administrator on the chosen project