Gain insights into app usage and security practices
Who can do this? |
Get insights into your organization’s people and app usage. You can use this data to:
track adoption of Atlassian apps
make data-driven decisions about who needs access to apps
evaluate the security of your organization.
View insights
To access your organization's insights:
Go to Atlassian Administration. Select your organization if you have more than one.
Select Security > Insights.
Available charts
Insights provide you with information about your organization’s Atlassian apps and security practices. You’ll only see insights when data is available to display, and you have an eligible plan for a chart. Most charts refresh automatically every 24 hours.
Users
Domains with access to your apps
A domain is associated with the email address of every Atlassian account that has app access in your organization. The chart shows the total number of managed accounts and external users from each domain with access to at least one app.
You can use insights from this chart to decide if you want to verify domains and claim accounts to manage more Atlassian accounts. You can also update your approved domains under your user access settings.
Users with access to your apps
The chart shows the total number of managed accounts and external users that have access to your organization’s apps.
You can use insights from this chart to increase the number of accounts you manage in an organization. You need to claim accounts to make them managed accounts.
User security
Authentication for managed accounts
The authentication for managed accounts chart shows how your users log in to their Atlassian accounts. It shows the number of managed accounts that:
have two-step verification enabled
log in with single sign-on
don’t have two-step verification enabled
Opting into two-step verification helps improve your organization’s security posture. If only a few users have two-step verification enabled, we recommend you:
Encourage users to opt-in to two-step verification in their Atlassian Account settings. Explore how users can protect their Atlassian Account
Use an authentication policy to mandate two-step verification for managed accounts. Requires Atlassian Guard Standard. Understand authentication policies
Two-step verification for external users
The chart shows the total number of external users who have enabled or have not enabled two-step verification for their Atlassian account.
Different ways users have two-step verification enabled:
They can enable two-step verification manually in their profile
Their account is managed by another organization that requires two-step verification
If you notice that your external users don’t log in with two-step verification, you can create an external user policy to require them to log in with two-factor verification to access your apps.
External user policy
The numbers in the chart shows the number of external users who are covered by an external user policy. The external user policy allows you to require two-step verification for external users to to access your apps. This policy applies security settings to all external users in your organization.
Mobile usage
Mobile app usage
The Atlassian mobile app usage chart shows the distribution of mobile app users within your organization. The figures reflect the total number of users who accessed content in your organization from one of these Atlassian mobile apps:
Confluence
Jira
Loom
Opsgenie
You can manage mobile app security risks with mobile app policies.
Mobile device usage
This chart shows the type and number of mobile devices that accessed Atlassian mobile apps in the last 12 months. User totals include managed accounts and external users.
User activity
These chart require Atlassian Guard Standard or a Premium plan.
Active users
The active users chart shows users who have viewed a page in a product (such as a Jira issue or Confluence page) during the selected date range. In the case of Trello, users who used Trello at least once a month and have a verified email domain are active.
Active users by app
The active users by app chart shows users that are active compared with those who aren’t currently active, categorized by app. Totals include users who were active during the selected date range, even if currently deactivated.
Active Trello users
The active Trello users chart shows the number of users from your verified domains who logged in to Trello within the selected date range. The chart breaks down users by pricing plan.
Jira usage
These charts are unable to collect real-time data, preventing a manual refresh. Instead, they will automatically refresh once data becomes available. These charts require Atlassian Guard Standard or a Jira Premium plan.
Jira usage activity
The Jira usage activity chart shows the number of active users and seats that you pay for. These details provide you with a usage rate that represents active users who have logged in at least once in comparison with the seats you’re paying for.
Insights from this chart allow you to identify who you want to re-invite.
Jira issues activity
This chart displays your done rate, issues done, and issues created. The done rate is the number of issues marked as done in comparison with the number of issues created.
Insights from this chart can help you gain a better understanding of how your team manages Jira issues. A higher done rate indicates a greater number of issues that have been marked as done. You can utilize these insights to improve practices for handling issues and managing sprints.
AI usage
Active AI users
This chart requires at least one app with AI activated, and shows active users who used an AI-powered feature at least once in a period of one month.
You can filter this chart by date range to view usage trends over time, and if your organization has multiple sites with Atlassian Intelligence activated, you’ll also have the option to filter user activity by site.
Requests sent to Rovo
Some Rovo data may not be available until 30 days after activation.
This chart requires at least one site where Rovo is activated. It displays usage trends based on the total number of requests sent to Rovo Chat and agents.
Was this helpful?