Organizations, roles and modules

Acest conținut nu este încă disponibil în limba selectată.

Three separate things decide what appears on your screen in kOS. They are worth untangling, because “I can’t see X” has a different fix in each case.

Your organization — the tenant whose data you are looking at.
Your role and permissions — what you may do inside it.
Your product’s modules — which parts of the product exist at all.

Organizations

An organization is a tenant: a law firm, a notary office, a clinic, a team. It owns the records, documents, knowledge bases and assistants you work with, and it is the boundary that kOS enforces. You see your organization’s data and no one else’s.

You join an organization by invitation. Membership carries exactly one role, and a person can be a member of several organizations — with a different role in each.

Only one organization is ever active at a time. If you belong to more than one, kOS asks you to choose on the Select organization screen when you sign in, and afterwards you switch from the sidebar. Nothing you do in one organization is visible from another.

Central administration of several organizations

Some arrangements have one organization that centrally administers others — a network administering member offices, for example. Where that applies, the administering side sees a Client organizations list (in Med, Clinics) and can create offices, invite their first administrator, and manage their settings on their behalf. From inside an office nothing looks different; the office’s own administrators still manage their own team.

There is exactly one level of this. An office cannot itself administer further offices, and there are no teams or departments inside an organization — the way to give someone narrower access is their role and permissions, not a sub-group.

Roles

A role is a named bundle of permissions. Two roles are available for an administrator to assign:

Role	What it can do
Organization Member	Use the assistants and the knowledge base; create and edit assistants and reusable prompts; view the organization’s Usage and Audit log.
Organization Admin	Everything a member can, plus invite and remove people, change their roles, edit per-person permissions, and manage API keys.

A third role, Organization Owner, can appear on your member list. It cannot be given through an invitation or a role change: ownership is set by KlusAI. If you created your organization yourself by signing up, you are its Organization Admin.

Med has its own roles for clinic staff, granted through Med’s own invitation flow rather than the general one — among them Med Physician and Med Clinic Admin. See Med.

The table says what each role is permitted to do. Which of those pages your product actually shows is a separate question — see What each product’s Organization section contains.

Three rules govern who can grant what, and each exists to prevent a specific accident:

You can only assign a role whose permissions you already hold in that organization. An administrator cannot promote someone past themselves.
You cannot change or remove your own membership. Another administrator has to do it.
The last administrator cannot be demoted or removed. Appoint a second one first, or the organization would be left with nobody who can administer it. The same goes for the owner: only an owner can change or remove the owner’s membership.

Per-person permissions

Roles are deliberately coarse. On top of a role, an administrator can switch individual capabilities on for one person, under Organization → People. Neither Lex nor Med shows the People page; in those products, what a person can do is decided by their role.

Use the assistants (chat) — on for everyone, and not removable.
Manage AI assistants — create and edit the assistants and their setup.
Manage the toolbox — decide which tools each assistant can use.
Manage the prompt library — add and edit reusable prompts.

These grants only ever add. Anything the person’s role already includes shows as on and locked, marked as included with their role, so there is no way to use this screen to quietly take access away.

Modules

A module is a whole area of the product — Documents, Knowledge, Team, and the domain areas each product brings: clients, matters and deadlines in Lex; patients, consents and the pathology library in Med; GPU inference and the API in razorBridge.

Two things gate a module, and the distinction matters when something is missing:

Whether your organization has it is set by KlusAI, as part of what you have subscribed to. There is no switch for this inside the Hub, for you or for your administrator — if your organization needs a module it does not have, that is a conversation with KlusAI, not a setting.

Whether you see it is your role and permissions. If a colleague can see a section and you cannot, that is the part an administrator can fix today.

What the assistant can reach

The same three layers apply to Klu. Its toolkit is scoped to your product, so a Lex assistant has legal tools and no clinical ones. Within that, it can only reach records you are allowed to see — asking the assistant is not a way around a permission you do not have. And an administrator can narrow it further per assistant through the toolbox.

What each product’s Organization section contains

The Organization section is assembled per product and per person, so it is not the same everywhere:

Lex — an Organization Admin sees Members. Assistants, Elements, Usage, Audit log and Branding are kept for the organization’s owner, so a firm’s administrators and members do not see them. A plain member has no Organization section at all.
Med — the generic Usage, Audit log, Elements, People, Branding and API keys pages are not part of Med. A clinic is administered from Med’s own Clinic admin section. See Med.
razorBridge — has its own navigation rather than this section. See razorBridge.

Accountability

Two read-only surfaces let an organization see itself:

Usage — your organization’s consumption.
Audit log — what happened in your tenant, with tabs for Changes, Sign-in & security, AI sources, Configuration and Deletions.

Neither is currently shown to a Lex firm’s own members or administrators, and Med does not include them; see the list above.

Administering your organization — the how-to: inviting people, changing roles, language.
The Hub — where these sections live on screen.