> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/data-security-documentation/inventory-and-monitoring/dashboards-and-reports/access-and-visibility-for-dashboards-and-reports.md). # Access and visibility for dashboards and reports Access to all dashboard and report data is strictly controlled through Role-Based Access Control (RBAC) and Scope-Based Access Control (SBAC). These permissions determine the objects and data a user can see, and dictate how data behaves when elements are copied or shared across different users: * **RBAC:** Controls access to dashboards and reports as separate objects.\ Your role must grant you access to view or edit these objects, as defined by your administrator. For more information about the RBAC permissions required, see [Dashboards and Reports permissions](/cortex-xsiam/reference-and-developer-docs/role-based-access-control/dashboards-and-reports-permissions.md).\ In addition, your administrator must define specific permissions to enable sharing of custom dashboards and report templates, for more information, see [Manage access to objects](/cortex-xsiam/onboard-cortex-xsiam/post-deployment/manage-user-roles-and-access-management/manage-access-to-objects.md). * **SBAC:** Controls the display of data according to your authorized data scope.\ Dashboard and report data is automatically filtered based on your authorized data scope. For example, you will only see information for the asset groups you are permitted to view.\ If you have access to a shared dashboard or report but lack the required data scope for the underlying datasets, the dashboard will load, but the widgets may appear empty or display an error. For more information on defining SBAC, see [Manage user scope](/cortex-xsiam/onboard-cortex-xsiam/post-deployment/manage-user-roles-and-access-management/manage-user-scope.md). --- # 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://cortex-docs.paloaltonetworks.com/data-security-documentation/inventory-and-monitoring/dashboards-and-reports/access-and-visibility-for-dashboards-and-reports.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.