Track User Activity
Activity & last seen is a screen in the Advanced User Manager console sidebar, under MANAGE. It answers one question: which accounts have stopped being used, so you can deactivate them and reclaim licensed seats.
The screen header reads Find and reclaim inactive accounts.
Before you start
Every operation in the app requires Jira administrator permission. Without it you will see empty lists rather than an error message, which can look like a bug.
The screen is also empty until you import last-seen data. Atlassian does not expose last-seen dates through an API, so the app reads them from the CSV export you download from your organization's admin site.
1. Import last-seen data
Last-seen dates come from the user export at admin.atlassian.com (Directory / User management → Export users). You can start the import from three places:
The Import last-seen data button in the top-right corner of Activity & last seen.
Jira users → Add users → Import last-seen data.
The Import last-seen CSV quick action on Overview.
The importer matches columns by product name and accepts the current Atlassian export headers, for example Last seen in Jira - <site>, plus Jira Service Management, Confluence and Compass. It deliberately does not treat Never accessed as a date — those users are counted as never seen instead of being given a bogus timestamp. If the file contains no recognisable last-seen column the importer refuses it and tells you so.
Full walkthrough: How to import last seen dates ?
2. Read the Activity & last seen screen
Stat cards
Card | What it tells you |
|---|---|
Last-seen data | How many of your managed users have a Jira last-seen date, out of the total. This is your coverage figure — if it is low, the rest of the screen is based on a small sample. |
Inactive 60+ days | Users whose last Jira activity was more than 60 days ago. Review & deactivate → takes you straight to Jira users with the status control already switched to Inactive. |
Active this week | Users seen in Jira in the last 7 days. |
Inactivity distribution
The left panel breaks your users into five buckets, measured from the imported Jira last-seen date:
Bucket | Meaning |
|---|---|
Active this week | Seen in the last 7 days. |
8–30 days ago | Normal for part-time or occasional users. |
31–60 days ago | Worth a look. Often people who changed teams. |
61–90 days ago | Strong candidates for deactivation. |
90+ days / never | Includes users with no last-seen date at all (exported as Never accessed). Check these against your leavers list first — a missing date can also mean the export simply did not cover that product. |
Coverage by product
The right panel shows what percentage of your users have a last-seen date for Jira, Confluence, Service Mgmt and Compass. Import per-product exports to raise coverage; higher coverage means the inactivity buckets describe more of your directory.
Least recently active
A shortlist of the six users with the oldest Jira last-seen date, each with their status and a Deactivate button. View all inactive opens the full list on Jira users.
3. Show last-seen dates in the Jira users table
There is no separate last-seen field picker. Last-seen dates are ordinary table columns on Jira users, switched on in the Columns popover:
Open Jira users in the sidebar.
Click Columns in the toolbar, to the right of the Active / Inactive / All control.
Under Last-seen columns, toggle Jira, Confluence, Service Mgmt or Compass. The Confluence, Service Mgmt and Compass columns are off until you turn them on, so if you have imported that data and cannot see it, this is why.
The same popover has a Property columns section listing your custom user properties, if you have defined any.
Only three columns are sortable: User, Status and Seen · Jira. Click Seen · Jira to bring the stalest accounts to the top.
This screenshot shows an earlier version of the interface. The steps in the text above are current.
The status filter defaults to Active.
On Jira users, the Active / Inactive / All segmented control opens on Active. Accounts you have already deactivated are therefore hidden until you switch it to Inactive or All. This is the single most common source of "my users have disappeared" reports — check this control before assuming anything is missing.
4. Act on stale accounts
Once you can see the dates, work through them from Jira users:
Sort by Seen · Jira, or arrive from Review & deactivate → / View all inactive on the Activity screen.
Set the status control to All if you want to confirm that an account is not already deactivated.
Tick the rows you want to act on. A floating selection bar appears at the bottom of the screen.
Choose Deactivate in the selection bar. The app pre-checks every selected account and shows an amber panel listing any it cannot change, before anything is sent.
Confirm. Deactivation frees the licensed seat and is reversible — you can activate the same account again later.
Activate and deactivate only work for managed accounts, and they need an organization API key created without scopes. Both requirements, and the errors you see when they are not met, are covered on Deactivate/Activate Managed-Accounts. Read that page before your first bulk deactivation.
This screenshot shows an earlier version of the interface. The steps in the text above are current.
Exporting what you found
To keep a record of the accounts you are about to deactivate, select the rows on Jira users and use the CSV export in the floating selection bar. The export covers the selection only — there is no button that exports the whole directory.
Good to know
Last-seen tracking applies to Jira users only. External users are Service Management customers and do not have Jira access, so there is nothing to report on for them.
Last-seen data is a snapshot of the CSV you imported, not a live feed. Re-import the export periodically to keep the buckets honest — the Last-seen data card shows when the last import ran.
Every deactivation and activation is written to the persistent activity log shown under Recent activity on Overview.