> For the complete documentation index, see [llms.txt](https://docs.guardware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guardware.com/documentation/management-console/frequently-asked-questions/management-console-related-faqs.md).

# Management Console related FAQs

<details>

<summary><strong>Can I create a monitoring-only user who can view selected screens but cannot configure policies?</strong></summary>

User access control is not available in the current version. We’re working on it for a future release. It will let administrators control which screens a user can access and whether they have read-only or write access.

</details>

<details>

<summary>How can a user reset a forgotten password?</summary>

All user accounts are email-based. Select **Forgot Password** on the login screen to request a reset link. If you don’t receive the email, ask an administrator to log in and help you reset your password.

</details>

<details>

<summary>What should I do if I don’t have access to Microsoft Purview or a license to preview classifications when adding data classifications?</summary>

You can add classifications manually using the product’s own classification option. The console supports both Microsoft Purview-based classifications and custom classifications.

</details>

<details>

<summary>What should I do if permissions are missing after integrating Microsoft 365?</summary>

Click **Run Check** to verify and grant the recommended permissions. If your organisation has concerns about specific permissions, you can review or remove them in Microsoft Azure. Contact the GuardWare Support team to understand how changing those permissions may affect the integration.

</details>


---

# 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.guardware.com/documentation/management-console/frequently-asked-questions/management-console-related-faqs.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.