# Settings

A Setting is a constant value that you can use throughout your application. The application can never change a setting's value, only you can.

You can also mark a Setting as *"secret"*, which will ensure that any personal or sensitive data stored in that Setting will remain secure, e.g passwords, usernames, ID numbers, etc.

The use of Settings will contribute to quick and easy maintenance of your application and is especially useful when you want to publish one application in multiple environments and need different values. This could, for example, be folder or file names.

Another benefit of using Settings is that their values can be changed on Application Manager, without having to redesign or redeploy your application.

***

{% embed url="<https://www.youtube.com/embed/5LQMr9LDvX4?autoplay=1&rel=0&vq=1080>" %}
Add a Setting
{% endembed %}

***

### How to use Settings

1. Provide a name and value for a setting.
2. Select the *Secret* checkbox if required.
3. Assign Settings to relevant properties (e.g. a control's property).
4. If required, change setting values as part of the application publishing process or on Application Manager after publishing.

*Note:* Stadium will not export the value of a secret from the Designer to Application Manager when the Application is deployed. The value of secrets must be provided as part of the publishing process or on Application Manager.

***

![](/files/sXRx3uzUNB6lagEKwlM5)

![](/files/2smrqqbDE7deVtemk46V)


---

# Agent Instructions: 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:

```
GET https://docs.stadium.software/features/settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.