Organisations, teams and members

An organisation is your firm’s private space in Hebno. Teams set which models and limits apply to people, roles determine who can administer, and projects contain the work. Knowing which layer controls what avoids looking in the wrong place.

​

The layers

One person can belong to more than one organisation. Each membership has its own teams, settings and connections.

​

Organisation

The organisation contains everything shared: the list of members and teams, the models the firm has enabled, spend limits, which integrations are allowed, the Library, the organisation context included in every chat, and settings such as chat memory. Owners and admins manage it under Admin. Members do not see the Admin section. Organisation branding (name, logo, primary colour) appears in the sidebar and invitations, and the name and logo appear on built-in Word documents.

​

Teams

A team groups members for three purposes:

• Model access. The organisation enables models. A team can narrow that set. A member gets the models their organisation allows, minus any a team restricts.
• Spend limits. Limits can apply to the whole organisation, a team, a member or a project. See Spend and limits.
• Attribution. Usage is recorded against the member, team, project and model, so admins can see where spend goes.

A member can belong to several teams, and every member belongs to at least one. A chat can be tagged to a team. When you belong to exactly one team, Hebno selects it for you. Teams are administrative groups: they do not replace roles, and a person on any team can be an admin. Every organisation has at least one team. Deleting a team removes its model and limit assignments, and members retain their accounts and other teams.

​

Members and roles

Every member has one organisation role. Owners and admins grant the admin or member role when they invite someone or edit them under Admin → Members. Ownership cannot be granted by invitation or domain access. An admin can suspend a member, who then loses access immediately while their account and history are kept, and reactivate them later. See Roles and permissions.

​

Projects and who sees them

A project has its own members and two project roles: admin and member. Project admins change the project’s details, brain and member list. Organisation owners and admins can manage every project. Each project needs at least one admin. Chats tagged to a project appear on its Sessions tab, shared with project members by default. Mark a chat Private to hide it from teammates. Sharing a chat with a specific person is a separate action. See Share a chat.

​

How a member joins

People join by invitation (the invitation sets their role and teams), or through domain access, where anyone with a verified company email domain joins automatically with a role and optional starting team the admin chose. See Join your organisation and Members.

​

Next steps