# Enterprise controls

Source: https://athas.dev/docs/enterprise

Understand managed workspaces, integration allowlists, and organization AI policies.

Enterprise workspaces can apply policies to desktop configuration and AI access. Your account
must have enterprise workspace access; ordinary local projects do not create an enterprise policy.

## Inspect the policy

Open **Settings > Enterprise** while signed in. Administrators can update policy controls;
other members see the policy in read-only form. If the policy cannot load, refresh your session
before assuming a control is unavailable.

## Available controls

| Control               | Purpose                                         |
| --------------------- | ----------------------------------------------- |
| Managed mode          | Apply organization management to settings       |
| Integration allowlist | Restrict installed integrations to approved IDs |
| Bring your own key    | Allow or restrict personal provider keys        |
| AI completion         | Enable or disable AI completions                |
| AI chat               | Enable or disable AI chat                       |

Administrators enter integration IDs in the allowlist, separated by commas or newlines, and save
the policy. Use the catalog's actual IDs rather than display names.

## When a setting is locked

A disabled control can reflect organization policy. Ask your workspace administrator to inspect
the policy; changing a local setting is not a way to override it. A policy restriction and a
missing provider key are different causes of unavailable AI.

See [Providers and Models](https://athas.dev/docs/ai-providers) for model setup, [Integrations](https://athas.dev/docs/integrations)
for the catalog, and [Enterprise](https://athas.dev/enterprise) for organization rollout options.