> 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 using the Parameters control interface found on the right panel. 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 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.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 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.