> ## 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 an AI work platform for client research and delivery: chat, research runs with sources, deliverables (Word, PowerPoint, Excel, email), projects, a shared library, agents, Office add-ins, and integrations with Microsoft 365, Google Workspace, CRM, project delivery, ERP and finance systems.
> Use British English (organisation, not organization).
> Every feature and integration described in these docs is available. Describe it as documented.
> Hebno never writes to a connected system without a member confirming a card. Finance and ERP writes are drafts only.
> Do not discuss commercial terms. Direct commercial questions to support@hebno.com.
> Start with /index and /get-started/quickstart.

# Models

> Choose which models your organisation can use, restrict them per team, and understand how Auto picks within what a member is allowed.

Models control what members can choose in the chat model picker. You set an organisation-wide list first, then optionally narrow it for individual teams. Find the page under **Admin → Models**. It has two tabs: **Organisation** and **Teams**.

## How access resolves

A member can use a model only when both of these are true:

1. The organisation has enabled it.
2. Their team has not disabled it.

A team can never use a model the organisation has switched off. If a member belongs to several teams, the chat's team tag sets which team's list applies.

## Organisation tab

The **Organisation** tab shows a card for each model provider. Open one to enable or disable its models for your organisation.

* Each model shows a capability tier (**Fast**, **Balanced** or **Powerful**) and its context size.
* **Enable all** switches on every model from that provider.
* A model the provider has withdrawn shows **Retired** and cannot be enabled.

Enable at least one model, or members have nothing to chat with.

> [!NOTE]
>
> Enabling a model at organisation level does not add it to teams that already have custom restrictions. Hebno shows how many teams were not updated and links to **Review team access**. Add the model to those teams from the **Teams** tab.

## Teams tab

The **Teams** tab lets you give different teams different models. Changes apply on top of your organisation-wide settings.

Each team shows one of two states.

| State | Meaning |
| - | - |
| **Inheriting org defaults** | The team uses every model the organisation has enabled. |
| **Custom restrictions** | The team uses a chosen subset. The count shows how many of the available models are on, for example "4 of 7 models". |

**1. Open the team**

On the **Teams** tab, select **Manage** next to the team.

**2. Choose models**

Switch models on or off, or select **Enable all models for this team**. Models the organisation has turned off show **Org disabled** and cannot be switched on.

**3. Save**

Save the changes. They apply to the team's next chat.

Select **Reset to organisation defaults** to remove a team's custom restrictions so it inherits the organisation list again.

## Auto

**Auto** is a choice in the model picker. When a member selects it, Hebno picks a suitable model for each message from the models that member is allowed to use. It never picks a model the organisation or the team has disabled, so a restriction you set applies to Auto as well.

Members can also set a **Default model** in **Settings → Chat preferences**, including **Auto**, which applies to every new chat they start.

## When a model is removed

If a member's saved model is later disabled or retired, their next chat shows **This model is no longer available** and offers a choice of another model or **Auto**. Existing conversations retain their history.

## Choose a sensible setup

* Enable a fast model and a more capable model for the whole organisation. Members choose by task.
* Restrict a team only when you have a reason: a client contract, a cost-conscious practice, or a team that does only light drafting.
* Pair model restrictions with a team [limit](https://hebno.com/docs/admin/limits.md) so a restricted team is governed on both access and spend.

Changes to model access are recorded in [Logs](https://hebno.com/docs/admin/logs.md) under **Models**.

## Next steps

* Read [Models](https://hebno.com/docs/concepts/models.md) for how members choose between them.
* Set [spend limits](https://hebno.com/docs/admin/limits.md) per team.
* Create or edit [teams](https://hebno.com/docs/admin/teams.md).


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