> For the complete documentation index, see [llms.txt](https://docs.drivepoint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drivepoint.io/using-the-web-app/advanced-permissions.md).
# Advanced Permissions
Linking your Microsoft Account to Drivepoint to configure the Plans page access.
### **What are Drivepoint's Advanced Permissions?**
Drivepoint’s **Advanced Permissions** give you fine-grained control over who in your organization can view and edit financial data, plans, and reports. This ensures sensitive information is only visible to the right people while keeping the rest of your team productive with the tools and dashboards they need.
With Advanced Permissions, you can:
* **Hide financial reports** from non-financial users or department specific users
* **Restrict plan actions** (e.g., setting a live model, using Quick Edit, importing financials) to approved roles
* **Link with Microsoft SharePoint** so users only see the Plans they have permission for on the Drivepoint Plans page
* **Protect sensitive financial imports** from QuickBooks Online or NetSuite. For example, only allow financial users to import financial information into any Drivepoint Plan.
**What does this mean for your team?**\
Non-financial users can still collaborate in Drivepoint without accessing sensitive data, while finance and leadership teams retain full visibility and control.
**How to set up Advanced Permissions**\
Advanced Permissions are configured at the account level and, in some cases, require enabling a feature flag (such as SharePoint linking). If you’d like to turn them on or adjust your group permissions:
📧 **Contact our team** at or reach out to your Drivepoint Customer Success Manager. We’ll walk you through the best setup for your organization and help ensure your reports, plans, and dashboards are secure and compliant.
---
# 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.drivepoint.io/using-the-web-app/advanced-permissions.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.