Release Notes
Current release
This is the largest update to Advanced User Manager since launch. The admin screen has been rebuilt as a console, several features changed behaviour, and older screenshots elsewhere in this space may still show the previous interface.
Redesigned admin console
The old tab bar is gone. The app now opens on a console with a left sidebar grouped into MANAGE (Overview, Jira users, External users, Activity & last seen) and CONFIGURE (User properties, Automation, Custom fields, Get started).
Jira users and External users now carry count badges in the sidebar.
New Overview dashboard: four stat cards (Managed users, Active accounts, Inactive, External customers), a Needs attention panel, a Last-seen coverage card for Jira, Confluence, Service Mgmt and Compass, Quick actions and Recent activity.
New Activity & last seen screen for reviewing account usage in one place.
New Theme control in the sidebar footer: Jira (follows your Jira appearance setting), Light or Dark. The footer also holds Documentation & support and the build label.
Jira users table
New Columns popover with two sections: Last-seen columns (Jira, Confluence, Service Mgmt, Compass — all off by default) and Property columns, one per custom user property you have defined.
CSV export: select rows, then use Export in the floating selection bar. It exports the selection only — there is no export-everything button.
Sorting is available on User, Status and Seen · Jira.
The status control on Jira users (Active / Inactive / All) defaults to Active, so deactivated accounts are hidden until you switch it. If a user seems to be missing, check this first.
User properties are now managed in the app
Go to Configure → User properties to create, rename and delete property definitions. Names are 3–20 characters and must be unique.
Renaming a property is safe — stored values follow the property, not its name.
Deleting a property removes the definition only. Values already stored on users remain, they simply stop being displayed.
Properties drive the Set properties drawer, property columns, CSV export, the workflow condition, validator and post function, and the External User Picker fields.
External users and Service Management customers
Add as customer now does two things: it creates a real Jira Service Management customer account, and it grants portal access on a service desk you choose in the drawer from a picker of the site's service desks. Customer accounts are unlicensed.
No email is sent to the new customer. Recipients use Forgot password on the portal to set a password.
Deleting an external user now offers a checkbox, Also revoke their Service Management portal access.
Adding and removing customers requires the signed-in admin to be a service desk administrator on that project. The app performs these actions as you.
Known limits, stated honestly: removing a customer never deletes their Atlassian account — no API can do that, only an org admin by hand. Removed customers still appear in the site-wide customer list and on requests they already raised. Customers cannot be removed from a service desk with open access (Atlassian returns a 400); on such a project the customer list does not control access anyway — set Project settings → Channels & self-service to "Customers added by agents and admins" to restrict it. Customer organization membership is a separate access path that removal does not touch.
Activate / deactivate
Before running, the app now pre-checks every selected account and shows an amber panel listing the ones it cannot change, so nothing fails silently mid-run.
When Atlassian rejects a change, the app reports Atlassian's actual reason instead of a generic error. For example, 403 "Caller must be a verified org admin of targeted account" means the account is not a managed account of the organization that owns your key.
Only managed accounts can be activated or deactivated — accounts in a domain your organization has verified and claimed under admin.atlassian.com → Directory → Managed accounts. Consumer domains such as gmail.com or outlook.com can never be managed. Accounts provisioned by SCIM or Google Workspace must be deactivated in the identity provider.
Deactivation frees the licensed seat and is reversible.
Correction to earlier documentation: the app stores both credentials and reuses them. The personal Atlassian API token plus your account email (created at id.atlassian.com → Security → API tokens) is used only for bulk-creating Jira users, and is entered once in the CSV import dialog. The organization API key (created at admin.atlassian.com → Settings → API keys) is used only for activate/deactivate and is kept in Forge storage. Earlier release notes and guides stated that the admin key "is never saved" — that was wrong. Rotate the key if it is ever exposed. The organization key must be created under API keys without scopes: the Atlassian user-management API is not covered by any scope, so a scoped key fails whichever boxes you tick.
Last-seen CSV import
The importer has been updated for the current Atlassian export column names. Export from admin.atlassian.com (Directory / User management → Export users), then use Jira users → Add users → Import last-seen data, or the Overview quick action.
Columns are matched by product name and now accept headers such as "Last seen in Jira - <site>", plus "Jira Service Management", "Confluence" and "Compass".
"Never accessed" is deliberately not treated as a date. If no recognisable column is found, the importer refuses the file and tells you so instead of importing nothing quietly.
Persistent activity log
Every mutating action is now recorded in a persistent activity log, shown under Recent activity on Overview.
Every operation in the app requires Jira administrator permission. Non-admins see empty lists rather than an error message, which can look like a bug.
6 July 2023
NEW “(AUM) Copy User Property” post function, “(AUM) User with specified value for property” condition and validator are now available !
22 May 2023
NEW Adding external users as customers is now possible !
30 March 2023
NEW Now it is possible to create external users to track their properties !
21 March 2023
BUGFIX Fixed bugs in user operations