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

# Attribution

> How team and project tags attach spend to groups and clients, and why tags are sticky on conversations.

Attribution connects each conversation's token cost to the right team and client work. Operators use it for internal chargeback and client rebilling.

## What gets tagged

Every **conversation** can carry:

| Field       | Purpose                                                 |
| ----------- | ------------------------------------------------------- |
| **Team**    | Which group owns the spend                              |
| **Project** | Which client or internal initiative the work belongs to |

Tags are chosen when the conversation is created.

## Sticky tags

Team and project tags are **sticky**. After creation:

* Retagging from the chat body is ignored
* Spend for the whole thread rolls up under the original tags

This keeps monthly reports stable. If attribution was wrong, start a new conversation with the correct tags.

## Projects and clients

Projects belong to the organisation. Each project has:

* A **name** (internal label)
* An optional **client name** (for client-facing reports)

Archived projects cannot be selected for new conversations.

Project tagging is optional. Your organisation can adopt it as internal policy even though Hebno does not require a project on every chat.

## Where attribution appears

Tagged spend flows into:

* **Admin → Overview** charts (by team, by model)
* **Usage** views for members
* **Limit checks** for team-scoped and project-scoped hard limits

## Filtering history

Members filter chat **History** by project from the sidebar. This helps find past client work without mixing unrelated threads.

## Example workflow

An agency delivery lead starts a chat:

1. Select **Team**: Client A delivery
2. Select **Project**: Website copy refresh (client: Client A Ltd)
3. Work in the thread over several days

All token cost for that thread appears under Client A delivery and the Website copy refresh project in admin reporting.

## Next steps

* [Using chat](/docs/guides/chat) - how to tag at conversation start
* [Spend and limits](/docs/concepts/spend-and-limits) - project-scoped limits