Roles and permissions

Hebno uses three organisation roles.

Roles

Role	Typical holder	Summary
Owner	Founder or account holder	Full admin access; cannot be suspended by others
Admin	Ops lead, IT-light owner	Full admin access except owner-only billing edge cases
Member	Individual contributor	Chat, personal settings, usage view only

Members with a completed onboarding state can:

Start and continue chats
Pick models allowed for their team context
Attach files to messages
Tag conversations with team and project at creation
Browse, rename, and delete their conversation history
Open personal Settings: name, theme, default model, custom instructions, memory (if allowed)
View Usage against limits assigned to them

Members see an Admin link in the sidebar but are redirected to chat if they open admin pages without an admin role.

Users with owner or admin role can access Admin:

Area	Actions
Overview	Date-range spend, KPIs, charts, top spenders
Members	Invite, suspend, reactivate (not self, not owner)
Teams	Create teams, assign members
Models	Enable org models, set team whitelists
Limits	Create and edit hard/soft limits by scope
Billing	View plan, seats, subscription status
Settings	Currency, chat memory policy, organisation context

Admins can suspend members. Suspended members cannot use Hebno until reactivated. Owners cannot be suspended. Admins cannot suspend themselves.

Invites specify email, team, and role. Pending invites appear on the members page until accepted or expired.

Admin changes (members, limits, models, settings) are recorded server-side. See Audit trail for how to review activity in Hebno.