> ## 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.

# Organisations and teams

> How workspaces, organisations, teams, and members relate in Hebno.

Hebno uses a multi-tenant workspace model. One person can belong to multiple organisations, each with its own teams, limits, models, and billing.

## Organisation

An **organisation** is your workspace tenant. It holds:

* Members and their roles
* Teams and team membership
* Enabled models and access rules
* Spend limits
* Billing subscription and display currency
* Organisation-wide settings (chat memory policy, organisation context)

The word **workspace** in onboarding refers to the same entity as **organisation**.

## Teams

A **team** groups members for spend attribution and model access. Examples:

* Delivery teams (Design, Engineering)
* Client-facing groups (Client A account team)
* Internal functions (Operations)

Every member can belong to one or more teams. Conversations record the team tag chosen at creation.

Teams do not replace roles. A member on the Marketing team can still be an organisation **admin**.

## Members

A **member** is a person's profile inside one organisation. Each membership has:

* Display name within the organisation
* Role: **owner**, **admin**, or **member**
* Team assignments
* Personal chat preferences (default model, custom instructions, memory toggle)

One global user account can have separate memberships in different organisations.

## Projects

**Projects** sit alongside teams for client work tagging. A project belongs to the organisation and can include an optional client name. Projects are used for:

* Tagging conversations at creation
* Project-scoped spend limits
* Filtering chat history

See [Attribution](/docs/concepts/attribution).

## Typical structure

```
Organisation
├── Teams (Marketing, Client A, …)
├── Projects (Website redesign, Q3 audit, …)
├── Members (each with a role)
└── Limits (org, team, member, or project scope)
```

## Admin vs member experience

| Capability                 | Member | Admin / owner |
| -------------------------- | ------ | ------------- |
| Chat                       | Yes    | Yes           |
| Personal usage view        | Yes    | Yes           |
| Admin overview and limits  | No     | Yes           |
| Invite and suspend members | No     | Yes           |
| Manage models and billing  | No     | Yes           |

See [Roles and permissions](/docs/concepts/roles-and-permissions).

## Next steps

* [Spend and limits](/docs/concepts/spend-and-limits) - how budgets attach to org, team, member, and project
* [Manage members](/docs/guides/manage-members) - invite and suspend teammates