> For the complete documentation index, see [llms.txt](https://docs.bsure.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsure.io/user-guides/power-bi/groups.md).
# Groups
This page gives you the opportunity to see members in one or more Entra ID groups, and by giving a cost to a group it makes it easy to allocate costs.
You can specify which groups You want to include in the report, set a cost per member of each group and give the groups a friendly name.
{% hint style="warning" %}
Visit [Customer Settings - Groups](/user-guides/customer-settings/groups.md) to add the groups you want to monitor in this report.
{% endhint %}
**Key benefits with report**
* Cost Allocation
* See members of groups with administrative privileges
Report will be empty until you follow instructions to [Configure which groups to show in the report](/user-guides/customer-settings/groups.md).
The report will show You all your specified groups in the Focus table with how many users and the total cost per group. The report itself has the same setup as the other reports with a focus table, a breakdown table and a user details table
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.bsure.io/user-guides/power-bi/groups.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
