> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/install/10.2-install/multidimensional-data-modeling-in-pentaho/analysis-schema-security.md).

# Analysis schema security

You can restrict portions of your OLAP schema from being viewed by certain user roles defined within your schema definition, and then map those role restrictions to the Pentaho Server so that when you publish the schema, its security restrictions are obeyed in Analyzer and Dashboard Designer (or any other Pentaho Server-based dashboard). If you do this, only the permissible parts of the schema will be available to the specified roles. Pentaho offers several unique paths to accomplish role-based security, all of which are explained later in this section.

Refer to the subsections below that apply to your situation.

**Note:** Changes to a OLAP schema should be done with Schema Workbench. If you change a schema, you must republish it to the Pentaho Server in order for the modifications to take effect. Changes to XML configuration files (such as those that contain core Pentaho Server and Mondrian engine settings or properties) can be done with any text editor.

* [Restrict Access to Specific Members](/install/10.2-install/multidimensional-data-modeling-in-pentaho/analysis-schema-security/restrict-access-to-specific-members.md)
* [Mondrian Role Mapping in the Pentaho Server](/install/10.2-install/multidimensional-data-modeling-in-pentaho/analysis-schema-security/mondrian-role-mapping-in-the-pentaho-server.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pentaho.com/install/10.2-install/multidimensional-data-modeling-in-pentaho/analysis-schema-security.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.