Skip to main content
Back to Integrations
Jira logo

Jira

Inventory Jira and Confluence: users, groups and membership, application-role seat usage, global settings, organization API tokens, the Marketplace apps installed in each product, Confluence spaces and who can see them (including anonymous and guest access), and the Confluence and organization audit logs.

Support

Questions you can answer 13

Each one is a saved query that ships with ConfigView, reading your Jira data on your own server. Ask it in plain English, SQL, Slack or the API.

  • Who changed Confluence permissions in the last 30 days?
  • Show recent Confluence admin changes
  • Has anyone exported a Confluence space this month?
  • Which Confluence spaces are open to large groups?
  • Which groups can edit or administer Confluence spaces, and how big are they?
  • Which deactivated accounts still have Confluence space permissions?
  • Do any leavers still hold space admin in Confluence?
  • Which Confluence spaces can people see without logging in?
  • Are any Confluence spaces open to anonymous users or guests?
  • Which Confluence spaces let guests create pages?

What ConfigView collects from Jira 11

  • Users

    Every account in the Atlassian site directory: name, email, account type (person, app or customer) and whether it is active.

  • Groups

    Every group on the Atlassian site. Groups are shared by Jira and Confluence.

  • Group Members

    Who is in each group, including deactivated accounts still listed as members.

  • Application Roles

    Jira product seats: licences bought, licences in use and the groups that grant each product.

  • Settings

    Jira global settings such as voting, watching, attachments and time tracking.

  • API Tokens

    Every user API token across the Atlassian organization: owner, label, created, last used and expiry. Needs the optional org-admin key.

  • Installed Apps (Jira + Confluence)

    Apps installed in Jira and in Confluence: name, vendor, version, enabled, and whether the customer installed it or it ships with the product.

  • Organization Audit Log

    The Atlassian organization audit log: who did what across Jira, Confluence and Atlassian Administration, from which IP and country. Needs the optional org-admin key and Atlassian Guard or Enterprise.

  • Confluence Spaces

    Every Confluence space: key, name, type (team, personal, knowledge base), status, who created it and when.

  • Confluence Space Permissions

    Who can do what in each Confluence space - users, groups, guests and anonymous visitors - and which spaces are open to people who are not logged in.

  • Confluence Audit Log

    The Confluence audit log: permission changes, space exports, group changes, app installs and admin setting changes, with who did it and from which IP. Needs a Confluence administrator.

Back to Integrations