> ## Documentation Index
> Fetch the complete documentation index at: https://docs.glissando.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> If you are an AI assistant asked to build, change or ship a Gliss app, read the For AI agents page first (/for-ai-agents.md on this site) and follow its steps.
> Inside an app's folder, the app's own AGENTS.md is the authority; `gliss guide` prints it. Never ask the user for a secret's value.

# Secrets

> Declaring the secrets your app needs, without ever writing their values.

> [!NOTE]
>
> **Coming in the first release.** This page describes behaviour being built for the first Gliss release. Details may change before it ships.

```yaml theme={null}
capabilities:
  secrets:
    SALESFORCE_TOKEN: credential
    SALESFORCE_URL: endpoint
```

* Declare only the name and the type. The app reads each secret as an environment variable of the same name.
* **`credential`**: a token or key. A guest outside your company may set it through a link, because they can only write it.
* **`endpoint`**: an address that decides where the app sends data. Only a signed-in member may set it, and Publish needs IT approval.
* Database passwords, AWS access and tokens between your own components are created by the platform. Do not declare them.

How values get set: [Secrets and mock mode](https://docs.glissando.dev/build/secrets-and-mock-mode.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.