> 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/customer-settings/user-management.md).

# User Management

Here you add users to Bsure Insights. After adding a new user, please provide the url new user and they will get instant access. More granular access possibilities in under development.

Bsure Insights will fetch all users in your Entra ID and you can add any of the member accounts as users in the application. Click Add Users button and select what role you want to assign to the users:

* System Administrator gives access to everything in the application
* Role Member gives access to Progress and what you choose to add

App features - the Global Data Access toggle gives access to Dashboard, Assessments, and drilldown into the underlying data behind each finding. *NB: These data can be considered sensitive.*

Set which Power BI reports you want to give users access to and press Next

Search for one or more users and add them to the list:

Click Add and you're done

We are currently building more roles and more options to offer individuals a more granular access to reports and content in the application.

You can change role or delete a user from Bsure Insights by clicking the square with the three dots to the right of each user.


---

# 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/customer-settings/user-management.md?ask=<question>&goal=<user_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.