> 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/support/frequently-asked-questions/grant-new-permissions.md).

# Grant new permissions

### Purpose

From time to time, new features in Bsure Insights may require additional Microsoft Graph permissions to be granted to the Bsure Data Collector.

When this happens, you will see a warning in the **System Status** page.

These warnings:

Do not stop Bsure from collecting existing data\
Do not affect current reports\
Do not interrupt normal operation

However:

You will not receive new functionality or insights until the required permissions are granted.

***

### When do you need to act?

You need to take action when the bell glows and Data Collector glows on the [System status page](/user-guides/customer-settings/system-status-page.md) with a warning:

<figure><img src="https://300487332-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FygloFyyKhIYtV62dMZJc%2Fuploads%2Fz27h1uZTCjfGJIHbxtYz%2Fimage.png?alt=media&amp;token=bb32145e-ce7e-4337-afea-7cc00c4b2f70" alt=""><figcaption></figcaption></figure>

A new feature requires additional permissions\
The System Status page shows a yellow warning on the Data Collector\
Missing permissions are listed

Example:

Missing permissions:\
Synchronization.Read.All

***

### Requirements

To grant new permissions, you must:

Be signed in to Bsure Insights\
Use an account that holds the Global Administrator role\
If required, activate Global Administrator in Azure PIM (Privileged Identity Management)

Without Global Administrator privileges, you cannot update the Data Collector permissions.

***

### How to grant permissions

#### Step 1 – Click the warning

Click the yellow Data Collector warning button.

This will open the Update Permissions wizard.

<figure><img src="https://300487332-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FygloFyyKhIYtV62dMZJc%2Fuploads%2F5TsqoLsNEQplSVVPbe7t%2Fimage.png?alt=media&amp;token=577ae264-860f-4154-a322-4062516c3860" alt=""><figcaption></figcaption></figure>

***

#### Step 2 – Review what will be updated

The wizard will:

Check current permission drift\
Locate the Data Collector service principal in Azure AD\
Connect to Microsoft Graph\
Add missing permissions

Example permission:

Synchronization.Read.All

Click Update to proceed.

***

#### Step 3 – Complete the update

After confirming, Bsure will:

Add the missing permission\
Validate the configuration

If successful, you will see:

<figure><img src="https://300487332-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FygloFyyKhIYtV62dMZJc%2Fuploads%2FBBzgKuiRgsiSizSjmbBl%2Fimage.png?alt=media&amp;token=49f4acdf-799d-46aa-9e16-ee878f071d9b" alt=""><figcaption></figcaption></figure>

Message:

Permissions have been updated successfully

Permissions Added: 1\
Permissions Removed: 0

***

### What happens after update?

Once permissions are granted:

New features depending on these permissions will activate\
New insights and reports will become available\
The System Status warning will disappear

There is no downtime and no impact on existing data collection.

***

### Troubleshooting

If the update fails:

Ensure you are Global Administrator\
Ensure your PIM role is activated\
Sign out and sign back in to Bsure Insights\
Try again

If the issue persists, contact Bsure support.


---

# 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/support/frequently-asked-questions/grant-new-permissions.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.
