> 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/pba/9.3-analytics/pentaho-dashboard-designer-cp/advanced-topics/secure-sql-filter-function-access.md).

# Secure SQL filter function access

The Dashboard Designer has a SQL filter for greater control over a database query. By default, this feature is restricted to administrative users.

Perform the following steps to change these settings:

1. Ensure the Pentaho Server is not currently running; if it is, run the `stop-pentaho` script.
2. Open the `/pentaho-solutions/system/dashboards/settings.xml` file with a text editor.
3. Locate the following line and modify it accordingly:

   ```xml
   <!-- roles with sql execute permissions -->
   <sql-execute-roles>Administrator</sql-execute-roles>
   ```

   **Note:** Values are separated by commas, with no spaces between roles.
4. Locate the following line and modify it accordingly:

   ```xml
   <!-- users with sql execute permissions -->
   <sql-execute-users>Administrator</sql-execute-users>
   ```

   **Note:** Values are separated by commas, with no spaces between user names.
5. Save and close the text editor.
6. Restart the Pentaho Server with the `start-pentaho` script.

The SQL filter function is now available in Dashboard Designer to the users and roles you specified.


---

# 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.pentaho.com/pba/9.3-analytics/pentaho-dashboard-designer-cp/advanced-topics/secure-sql-filter-function-access.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.