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

# Enable AI access for your organization

> Approve external AI and hosted keys separately, while members keep control of their own connections.

Organization channels start with external AI access **off**. An active owner or administrator decides whether members may connect them to ChatGPT or Claude.

## Administrator setup

<Steps>
  <Step title="Check organization permissions">
    Your organization plan must be active. In [organization permissions](https://zas.red/enterprise/permissions), enable agents in organization channels if your organization permits this use.
  </Step>

  <Step title="Open Organization AI access">
    Sign in with your registered Zas account and open [AI connections](https://zas.red/ai/connect). Find **Organization AI access**, choose your organization, and select **Manage AI access**. If prompted, confirm your sign-in.
  </Step>

  <Step title="Review the two approvals">
    Enable **Allow external AI apps to access approved organization channels**.

    Separately, enable **Allow Zas to hold encrypted connection keys so AI apps can work while members are offline**.

    Hosted ChatGPT and Claude connections require both approvals. Read the [data-handling explanation](/en/ai/privacy), then select **Save organization AI access**.
  </Step>

  <Step title="Let each member choose their channels">
    Members follow the ChatGPT or Claude setup guide and approve their own channel permissions. Admin approval does not connect every member or grant every channel automatically.
  </Step>
</Steps>

## What is checked during use

Zas checks current organization approval, active plan, membership and role, guest expiry, channel access, and the connection's Read/Send grants. Personal consent cannot override an organization restriction.

Your ChatGPT or Claude workspace may have its own admin approval. Zas organization approval does not change those provider settings.

## Turn access off

Return to **Organization AI access**, turn off external AI approval, and save. Subsequent connector operations are refused. You can disable an existing approval even if the plan or agents permission is no longer active.

Members can also [disconnect their own connection](https://zas.red/ai/connect), which removes its live hosted keys and revokes its dedicated agent. Turning access off cannot recall content already delivered to an AI provider.

[Local coding-agent policies](/en/agents/enterprise) are documented separately.


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