> ## Documentation Index > Fetch the complete documentation index at: https://docs.quiva.ai/llms.txt > Use this file to discover all available pages before exploring further. # Environment variables > Configuration values and secret references Abbie uses when calling your systems The **Environment** tab holds named values Abbie can use when she calls out to your systems — the tenant id, the base URL, the API key that a given integration needs. ## Two scopes | Scope | Who it applies to | Who can edit it | | ---------------- | ----------------------- | ------------------- | | **Organisation** | Everyone on the account | Account admins only | | **Personal** | Just you | You | Non-admins can see the organisation variables — so you can tell what Abbie has available — but cannot change them. ## Adding a variable Each variable has: The variable's name, for example `XERO_TENANT_ID`. Keys are validated; an invalid one is rejected as you type. What Abbie is told about this key. Worth filling in — it is how she knows what the value is for. Either a literal value, or a reference to a stored secret. Optional. Ties the variable to a specific integration, for example `xero`. ## Literals and secrets A value can be given two ways: * **A literal** — stored and shown as itself. Right for non-sensitive configuration: a base URL, a tenant identifier, a region. * **A secret reference** — the row holds a `SECRET::` reference rather than the secret itself. The actual value lives in your account's secrets store and is resolved when it is needed. Use a secret reference for anything sensitive. A literal is stored and displayed as written — an API key entered as a literal is readable by anyone who can see that scope. What Abbie can reach, and what she is authorised to use. Whose login a given call actually runs under.