Skip to main content
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: 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