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

> ## Agent Instructions
> Hebno is a B2B AI control platform for growing teams (30-250 people). Use British English (organisation, not organization).
> Describe only what Hebno supports today. If unsure, say so.
> Spend limits use the organisation display currency in the app.
> Start with /index and /getting-started/quickstart for Hebno orientation.

# Model access

> How organisations enable models, how teams inherit or restrict access, and member model preferences.

Hebno controls which models members can use through a layered access model: organisation catalogue, optional team restrictions, and personal preferences.

There is no separate policy screen. Access rules live in model enablement and team assignments under **Admin → Models**.

## Organisation level

Under **Admin → Models → Organisation**, admins enable or disable models for the entire workspace.

Disabled models disappear from the model picker for all members unless team-level rules say otherwise.

## Team level

Under **Admin → Models → Teams**, admins configure per-team access:

| Configuration               | Behaviour                                                                                           |
| --------------------------- | --------------------------------------------------------------------------------------------------- |
| **No team assignments**     | Team inherits all organisation-enabled models                                                       |
| **One or more assignments** | **Whitelist mode** - only models marked enabled for that team are available to members on that team |

Team restrictions apply when a member starts or continues a chat tagged to that team.

## Member preferences

Members can set a **default model** under **Settings → Chat preferences** when the picker is available. The default must still be enabled for the organisation and allowed for the member's team context.

Otherwise, new chats follow the organisation default unless the member picks a model in the chat model picker.

## Resolving the active model

When a member sends a message, Hebno resolves the model in this order:

1. Model explicitly chosen in the chat model picker
2. Member default model (if available in settings)
3. Organisation default model

The resolved model must pass organisation and team access checks for the conversation's team tag.

## Gateway

Hebno routes chat requests through its gateway to models enabled in your catalogue. In the app, members choose from model names in the picker - not from a separate provider menu.

## Next steps

* [Manage models](/docs/guides/manage-models) - enable and restrict models in admin
* [Using chat](/docs/guides/chat) - model picker and defaults for members