> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-user-manual/maps/sql-parameters/publishing-sql-parameters.md).
# Publishing SQL parameters
As an Editor user, you have the flexibility to determine wether SQL Parameters controls will be accessible in the public or shared version of the map. You can manage this from the "*Map settings for viewers*" section located at the top right of Builder interface.
Viewer users can then specify parameter values in the parameters bar above the map. This enables them to adjust the underlying data according to their unique needs.
{% hint style="info" %}
**This setting will allow Viewer users to select values and re-run SQL queries**.
Please be aware that in many cases this might produce a lot of different combinations of parameters that might not be cached in CARTO's CDN, and queries will reach the data warehouse and be executed, which might have a cost and performance implication.
{% endhint %}
---
# 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.carto.com/carto-user-manual/maps/sql-parameters/publishing-sql-parameters.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.
