opsen reads your Atlassian Cloud organisation: its sites and workspaces, every user, the products each can use, and when they last opened each one. It prices every product seat and finds people paying for a product they do not open.
Connect
Settings → Connections → Atlassian. An organisation admin creates an API key at admin.atlassian.com under Settings → API keys. Choose API key without scopes: Atlassian does not yet offer scopes for the user search and activity endpoints opsen reads. The key works for up to a year.
Atlassian does not report your plan through its API, so pick it: Standard, Premium or Free.
To count merged Bitbucket pull requests for the fee, also enter the Bitbucket workspace, your Atlassian account email and an API token with Bitbucket read access.
Prices
Atlassian prices per user in volume bands and publishes the average price for a team size, not the bands. opsen uses that average at your user count, monthly billing:
| Product | Standard, up to 100 users | Premium, up to 100 users | Standard at 1,000 | Premium at 1,000 |
|---|---|---|---|---|
| Jira | $9.70 | $19.60 | $7.34 | $11.81 |
| Confluence | $7.15 | $14.10 | $4.57 | $9.05 |
| Bitbucket | $3.65 | $8.00 | $3.21 | $6.88 |
| Jira Service Management, per agent | $26.90 (up to 10) | $61.60 (up to 10) | $10.88 | $28.40 |
Annual plans cost up to 17% less.
What it finds
| Finding | Rule |
|---|---|
| Inactive Jira, Confluence, Service Management or Bitbucket users | Product access with no visit in 90 days, or never; in the organisation for more than 30 days |
Atlassian counts a visit as viewing a product's page for two seconds. Its activity data can lag by a day.
Acting on it
Remove access takes the chosen product from each person in one click. They keep their Atlassian account, their other products and everything they wrote. Access given through a group cannot be removed person by person: opsen lists those, and you take the person out of the group in admin.atlassian.com.