> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/administer-and-govern/control/variables.md). # Variables Store reusable non-secret configuration values for a project or organisation. Variables store reusable configuration that is useful across operational work but is **not secret**. This distinction is technical, not cosmetic: Variable values are stored as ordinary plaintext values in the Lleverage application database and are rendered into runtime configuration. Do not use a Variable for anything that needs secret-storage guarantees. ### Scope and access Variables can exist at organisation or Project scope, and the Project surface combines the relevant values from both scopes. The current Variables router is **organisation-member scoped**, not Project-Builder scoped. An organisation member who can reach a Project can currently list, create, update and delete Variables for that Project. The Variables table exposes the entry's **Scope** as Organisation or Project and also shows whether the value is **In use**. ### Good uses Variables are suitable for values such as non-sensitive identifiers, environment labels, default configuration and reusable constants. They are not suitable for API keys, passwords, bearer tokens, client secrets, database connection strings or other credentials. Use [Secrets](/administer-and-govern/control/secrets.md) for those values. The product rejects database-connection-string shaped Variable input and directs you to the Secrets path. If a value would be harmful if copied into ordinary application storage, it is not a Variable. --- # 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.lleverage.ai/administer-and-govern/control/variables.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.