Administering your organization
Everything an organization, department, or team admin does: build the structure, bring people in, set the rules, and read the numbers. All of it is self-service.
1The model
An organization has three levels: the organization itself, departments inside it, and teams inside departments. People can belong to many departments and teams at once. Two invariants are enforced by the platform so membership never drifts: adding someone to a team also adds them to its parent department, and removing someone from a department removes them from its teams.
Every member holds one organization role plus any number of unit roles:
| Role | Scope | Grants |
|---|---|---|
| Org Admin | Whole org | Everything: structure, members, governance, install policy, invites anywhere, approvals everywhere |
| Publisher | Whole org | Creates and publishes org skills without admin rights (subject to approval settings) |
| Member | Whole org | Uses the registry; creates skills where settings allow |
| Department Admin | One department | Manages its members and teams, invites into it, approves its skills |
| Team Admin | One team | Manages its members and invites into it |
Admin rights nest downward (an Org Admin administers every unit; a Department Admin administers every team beneath them) and never sideways (a Department Admin cannot touch another department). Limits are generous: 500 members, 50 departments, 50 teams per department, 100 pending invites.
2Build the structure
From your organization page, open Departments. Create each department (name plus a short URL slug), then open its card to add teams. Departments come first; a team always lives inside one.
Add people to a unit from its member picker: it lists org members not yet in the unit, so nothing is typed by hand. Promote a unit admin by changing their unit role on the member list.
3Invite people
Open Members. Three ways in:
- Individual: a skills-hub username (existing account) or an email address (new users get account creation first). Both receive an email with an accept link, and you also get a share link to drop into chat.
- Bulk paste: a list separated by commas, spaces, or new lines. Each entry is processed independently; one bad address never sinks the rest, and you get a per-recipient result list.
- CSV upload: one username or email per row, first column.
Options on every invite:
- Org role: Member by default. Only Org Admins can grant Publisher or Admin on an invite.
- Department and team targeting: place the new member directly where they belong. Department Admins invite into their department, Team Admins into their team; untargeted org-wide invites are Org Admin only.
New members land in an onboarding flow that captures their departments, teams, and job role. Your only preparation is making sure the structure is accurate before invites go out, so people can find themselves in it.
4Set governance and install policy
The Governance page holds five toggles (approval for new skills, approval for modifications, member approvals, cross-department sharing, cross-team sharing) and the install policy (Open, Allowlist, or Blocklist for public catalog skills). What each does, and a recommended starting configuration, is covered in the Governance guide.
Changes apply immediately and are never retroactive: turning approvals on does not un-publish anything.
5Run the review queue
Pending approval requests appear at the top of the Governance page. Creations publish a new skill on approval; modifications promote a held version while the live version keeps serving installs. Org Admins review everything, Department Admins review their department's skills, and general members review only when the member-approvals toggle is on. No one reviews their own request. Every resolution lands in the permanent audit trail.
If two reviewers act on the same request simultaneously, exactly one resolution wins and the other is told the request was already resolved; the audit trail never contradicts the registry.
6Read the numbers
The Analytics page shows installs and active members over the last 30 days, skills by category, top skills, installs per day, and a per-department breakdown (members, skills, installs, active members) so you can see which parts of the organization have adopted the registry and which need attention. Every member can view it; nothing is editable.
7Housekeeping
- GitHub sync (optional): connect a GitHub organization to pull its members in automatically. Sync never removes anyone and never moves someone who belongs to a different skills-hub organization.
- Offboarding:removing someone from the organization ends all their unit memberships. Reassign their skills' ownership as part of the same motion.
- No lock-in: skills are plain markdown and exportable in full at any time.
Troubleshooting
| Symptom | Cause and fix |
|---|---|
| Invite link does not work | Expired after 7 days; revoke and re-send |
| "This invite is not for you" | Invitee is signed into a different account than the invite was addressed to |
| "Already belong to an organization" | One org per account; the invitee must leave their current org first |
| Member cannot see a teammate's skill | Scoping is working: the skill is department- or team-scoped. Add them to the unit or enable the sharing toggle |
| New skill "cannot publish" | Approval for new skills is on; the request is in the Governance queue |
| Install blocked | The install policy blocked a public skill; the error names the policy. Adjust it on the Governance page if wrong |