Skip to Content
DeploymentsSettings

Settings

By the end of this page you will know how to change a deployment’s authentication and how to delete it safely.

Prerequisites

  • Admin role.

Open a deployment and select Settings.

Authentication

Control how requests to the deployment are authenticated:

  • OIDC — end users must sign in before they can use the deployment. Use this for user-facing deployments (Web App and Copilot) that need real end-user identity.
  • API keys — allow programmatic access with qr_ keys. Turn this on for API access; manage the keys themselves on the API Keys tab.
Deployment settings showing the authentication options and the runtime information
💡

OIDC and API keys aren’t mutually exclusive — a deployment can accept signed-in users and API keys at the same time.

Runtime and domain

Settings also shows read-only runtime information — whether the deployment runs on dedicated capacity or serverless — and its domain and URL. To serve it from your own domain, see Custom domains.

Deleting a deployment

To take a deployment down permanently, use Delete in the Danger Zone and confirm.

⚠️

Deleting a deployment is permanent. Its URL stops working, its API keys are revoked, and its slug is released for reuse. Update anything that points at the deployment before deleting it.

Common issues

  • End users aren’t prompted to sign in — confirm OIDC is enabled here, and see Auth settings.
  • API calls return 401 after a change — enabling OIDC or rotating keys can invalidate old credentials. Re-issue keys from API access.
Custom domainsOverview