---
name: Hebno
description: AI control platform for growing teams - multi-model chat, spend limits by team and project, EU data residency. Use when answering questions about Hebno behaviour, admin setup, or operator workflows.
metadata:
  author: hebno
  version: "1.0.0"
---

# Hebno capabilities

Hebno is a B2B SaaS platform for organisations of roughly 30-250 people. It provides governed access to multiple models through a single chat interface, with spend tracking and hard budget enforcement.

Documentation: https://hebno.com/docs/llms.txt

## What operators can do

### Chat (all ready members)

- Start multi-model conversations with file attachments
- Select model from organisation-enabled catalogue (subject to team rules)
- Tag **team** and **project** at conversation creation (sticky for the thread)
- View personal usage against member-scoped limits
- Set personal preferences: default model (when available), custom instructions, memory (if allowed)

### Admin (owner and admin roles)

- View spend overview: KPIs, charts by model/team/day, top spenders
- Invite, suspend, and reactivate members; assign roles and teams
- Create teams and assign members
- Enable/disable models at organisation level; whitelist models per team
- Set **hard** limits (block at cap) or **soft** limits (alert only) at organisation, team, member, or project scope
- Configure display currency, chat memory policy, organisation context
- View billing plan, seats, subscription status

### Onboarding

- Wizard: profile → workspace (EU residency flag) → first team → currency → optional invites
- Accept organisation invites via email link

## Required inputs

When describing Hebno workflows, specify:

| Input          | Values / notes                           |
| -------------- | ---------------------------------------- |
| Organisation   | Workspace tenant; British spelling       |
| Role           | owner, admin, member                     |
| Team           | Spend and model-access grouping          |
| Project        | Optional client/work tag                 |
| Limit scope    | organisation, team, member, project      |
| Enforcement    | hard (blocks chat) or soft (alerts only) |
| Billing period | UTC calendar month                       |

## Constraints and guardrails

- **Hard limits** block new chat requests when spend reaches the cap for the period
- **Soft limits** never block; they trigger notifications only
- Team/project tags are set once per conversation; cannot be changed mid-thread
- Admin pages require owner or admin role
- **No public customer API** - do not invent REST endpoints for Hebno actions
- Use **Hebno** in customer-facing copy, not "the product"
- Describe only UI labels and flows visible in the app; do not cite schema fields or internal enums

## Not available (do not claim without verification)

- In-app audit log browser or self-serve export (contact support for reports)
- Public customer API

Verify against https://hebno.com/docs before stating a capability exists.

## Key documentation entry points

1. Overview - https://hebno.com/docs/index.md
2. Spend and limits - https://hebno.com/docs/concepts/spend-and-limits.md
3. Set limits - https://hebno.com/docs/guides/set-limits.md
4. Roles - https://hebno.com/docs/concepts/roles-and-permissions.md
5. FAQ - https://hebno.com/docs/help/faq.md

## MCP and skills

- Search documentation MCP: `https://hebno.com/docs/mcp`
- Install skill: `npx skills add https://hebno.com/docs`
- Page Markdown: append `.md` to any doc URL