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 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.