Members & roles
An organisation is the unit of tenancy in skillsvault: every skill, policy, connected machine, and audit event belongs to exactly one org, and the org slug is in the URL (/acme/...). This page covers creating an org, inviting people, and the roles that decide what each member can do.
Create an organisation
When you sign up, skillsvault prompts you to create your first organisation — just give it a name and you become its owner. Your first org is free to start; see Plans & entitlements for what each tier unlocks.
One free org per account
Creating additional organisations requires an existing paid org on your account. The first one is always free.
Invite members
Open Members in the console and choose Invite. Enter the person's email and pick a role:
Choose who can invite
Only an Owner or Admin can invite or remove members. Members and governance officers can see the team but not change it.
Send the invite
Enter an email address and select a role (Admin, Governance officer, Member, or Billing — you can't mint another Owner via invite). The invite appears in the members list as pending until it's accepted.
Mind the seat limit
A "seat" is an active member plus any outstanding invite. If adding one would exceed your plan's member cap, the invite is blocked with an upgrade prompt — the same limit is enforced in the console and on the server. On the Open (free) plan an org is capped at a single user; paid plans meter governed seats.
A member's row shows their role, status (active, invited, or suspended), when they joined, and when they were last active.
Roles & permissions
Roles are enforced everywhere — in the console UI and again on the server, so they can't be bypassed by crafting a request. There are five:
| Role | Can do |
|---|---|
| Owner | Full control, including billing and deleting the organisation. |
| Admin | Manage members, skills, policies, and namespaces. |
| Governance officer | Author skills and policies, and ratify suggestions. |
| Member | Browse the console, and submit skills for review. |
| Billing | Manage the subscription and invoices. |
Who can author and govern
Authoring skills, writing policies, and managing namespaces are write actions, available to Owner, Admin, and Governance officer. Members browse the registry, policies, fleet, and audit log without changing them, and can submit a skill or a change for review: it is published only when an owner, admin, or governance officer approves it.
| Capability | Owner | Admin | Gov. officer | Member | Billing |
|---|---|---|---|---|---|
| Invite / remove members | ✓ | ✓¹ | — | — | — |
| Author & publish skills | ✓ | ✓ | ✓ | — | — |
| Submit skills for review | — | — | — | ✓ | — |
| Approve submissions | ✓ | ✓ | ✓ | — | — |
| Write & activate policies | ✓ | ✓ | ✓ | — | — |
| Manage namespaces | ✓ | ✓ | ✓ | — | — |
| View console, fleet & audit | ✓ | ✓ | ✓ | ✓ | ✓ |
| Manage billing | ✓ | ✓ | — | — | ✓ |
| Delete the organisation | ✓ | — | — | — | — |
¹ Only the owner can make someone an admin (by invitation or by changing their role) or remove an admin.
Agent keys are separate from member roles
A developer's machine connects with an agent key, not their console login. Agent keys are scoped to the org and used by the CLI to pull skills and ship audit events — they don't grant console access. A key from skillsvault login carries its owner's role: anyone can connect a machine, but skillsvault publish works only for an Owner, Admin or Governance officer. Keys created in Settings → API keys (for CI) can publish.