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

# Approvals

> When Publish needs IT approval, and how to set the policy.

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

By default, an app's owner publishes their own app. IT approval is required when:

* the app's audience is `public`;
* the app uses an `endpoint` secret, which decides where data is sent;
* the project is at level 2.

You can require IT approval for every Publish, or loosen the defaults, in the catalog's `publish.approval` section. Major upgrades of the cluster or a database always need a person's decision.


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