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

# Sign-in (SSO)

> Company sign-in in front of your app, with no login code.

> [!WARNING]
>
> **Planned.** This page describes designed behaviour that is not built yet. Details may change before it ships.

```yaml theme={null}
capabilities:
  auth:
    type: sso
    audience: [group:finance, group:ops]
    roles: { admin: group:finance-leads, viewer: org }
```

* People sign in with your company's identity provider before a request reaches the app. People outside the audience never reach it.
* `audience` is `org`, one `group:<name>`, a list of groups, or `public`. A public app needs IT approval before Publish.
* `roles` maps app roles to groups. The owner can also give roles to people in the console.
* The app receives signed identity headers with the person's email, name, groups and roles. It must not write login code or add a sign-in bypass.
* Preview and Beta are always limited to the builder and the people they invite.

Field details: [gliss.yaml reference](https://docs.glissando.dev/reference/gliss-yaml.md#sso).


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