---
title: "Group usage"
canonical: "https://support.appfire.com/space/PA/198019187/Group%20usage"
format: markdown
---
> Macro (aura-html)

# How does Power Admin for Jira track the group usage?

This document explains how Power Admin identifies the usage and dependencies of groups in a Jira instance.

## Projects

Power Admin finds the total number of projects where the group is part of their configuration. It also detects more specific project information:

- **Security** - projects in which the group has access to their issues. You can click to view a list of the projects.
- **Notifications** -** **projects where group members will be notified of changes in these projects.
- **Workflows **-** **projects where the group is configured in workflows assigned to these projects.

## Shares and subscriptions

It also finds the filters and dashboards a group is accessing and the filters it is subscribed to:

- *Subscribed to filters* - Power Admin detects the filters group members are subscribed to.
- *Accessing filters* - Power Admin detects the filters shared with members of a group.
- *Accessing dashboards* - Power Admin detects the dashboards shared with members of a group.

## Configuration elements where the group is used

Power Admin finds all the *permissions, global permission, issue security schemes, events, workflow*s, *agile boards,* *filters, *and* service projects* that use the group by going through their JQL queries.

### Group to permission relation

Permission is shown as related to the group if:

- Permission is granted to the group.
- The group is associated with a project role in any project and this project role has rights to permission, which is part of a permission scheme used by the same project.

### Group to global permission relation

Global permission is shown as related to the group if it is granted to the group. 

### Group to issue security scheme relation

An issue security scheme is shown as related to the group if:

- The group is added to a security level of an issue security scheme.
- The group is associated with a project role in any project, and this project role is added to a security level of an issue security scheme used by the same project.

### Group to event relation

An event is shown as related to the group if:

- The group is configured as a recipient of notifications of an event.
- The group is associated with a project role (in any project) that is configured as a recipient of notifications of an event that is part of a notification scheme used by the same project.

### Group to workflow relation

A workflow is shown as related to the group if:

- The group is referenced in a property of a workflow participant.
- The group is associated with a project role in any project and this project role is referenced in a property of a workflow participant, which is part of a workflow that has assigned a workflow scheme used by the same project.

### Group to agile board relation

An agile board is shown as related to the group if:

- The group is referenced in a JQL entry (*Saved filter*, *Cardcolors*, *Quick filters*, *Subqueries*, *Swimlanes*).
- The group is a board administrator.

### Group to filter relation

A filter is shown as related to the group if the group name or id is referenced in the filter.

### Group to service projects

Dependency is detected when the group is referred to in *Request types*, *Queues*, *SLAs*, or *(Legacy) Automation rules*. Usage detection happens when the [service projects' cached index](https://appfire.atlassian.net/wiki/spaces/PA/pages/228229159) is generated for the first time or when it’s refreshed.