Skill servers
Create a server, choose which departments see it, rename it, make it public and delete it.
A skill server is a group of skills that belong together, plus who gets to see them. The most common split is one server per department, plus one shared server for the whole company (code of conduct, email templates, internal processes).
Your people do not connect to individual servers. They plug one key into the business hub, and the hub merges every server they're allowed to read. Split things into as many servers as you like and nobody has to configure anything twice.
Creating a server
Open Skill servers in the sidebar and hit New server.
Type a Name your team recognises at a glance, up to 100 characters, accents welcome.
Pick Who can see it.
With Whole business, every member sees this server through the hub. With Selected departments, you tick the departments that need it, and their sub-departments follow automatically.
Hit Create.
A Manager can only create servers scoped entirely inside their own branch, and can't pick Whole business. That option is locked, with a line explaining why. Business-wide servers are the Owner's and the Admins' job.
Each business has a server quota set by whoever runs the system (5 by default). The count sits at the right end of the toolbar as 3 of 5 servers. Out of slots and the New server button goes dim with the line You've used all 5 server slots. Delete one to create another.
The five tabs of a server
| Tab | What's on it | Who sees it |
|---|---|---|
| Overview | Numbers, the connection address, recently updated skills, recent calls | anyone who can view the server |
| Skills | The skill list, plus New skill and Upload a package | anyone who can view the server |
| Keys | Service keys csk_ for this server alone | Owners and Admins only |
| Logs | Every call into this server | anyone who can view the server |
| Settings | Rename, change scope, public or private, delete the server | only people who can manage the server |
Pick a tab you have no right to and the page falls back to Overview without an error. If you can look but not edit, a View only badge sits next to the server name.
Two views: List and Org chart
The Skill servers page has two tabs. List is a flat table with a search box and per-server numbers. Org chart draws the department tree, with each department's assigned servers and their skills nested underneath.
The tree answers the question a flat table cannot: which department can read this skill. The first branch, Whole business, holds the servers shared with everyone; the rest are your departments, nested exactly as your org chart is.
- Use the arrows to fold and unfold a branch. The first two levels open by default.
- A server assigned to several departments appears under every one of them, with an also in ... note so you know it is one server rather than a copy.
- The number on the right of a department counts the skills in the whole branch, sub-departments included.
- The tree reflects where a server is assigned, not everywhere it can be read: a server assigned to a parent department sits at the parent, and sub-departments still read it through inheritance.
Changing who can see it
Settings tab → the Who can see it card. Switch back to Whole business or tick different departments, then hit Save. It takes effect immediately: the next call from anyone in those departments already sees the server.
This is the cheapest way to widen or narrow read access. You reissue nothing, and you ask nobody to change their configuration.
Private and public
A server is Private by default: every call needs a valid key. In the Settings tab, Owners and Admins can flip the Visibility card so the server answers anyone who knows the address, with no key at all.
Think it through before you go public
A public server answers anyone holding the address. Only turn it on when the skills sitting there are safe to share outside the team. Even when it's public, a key that is wrong or revoked is still refused: the system never quietly falls back to anonymous.
A server's address is 16 random characters, unguessable and meaningless. But don't treat the address as a secret, because it sits in every config snippet you hand out. The key is the secret.
Deleting a server
Deleting a server deletes every skill and every key inside it. Anyone connected loses access immediately, and there is no undo. Usage logs are kept so you can still audit.
Settings tab → the red Danger zone card → Delete server, then confirm in the dialog.
Which servers a Manager runs
- A Manager sees business-wide servers and servers scoped inside their own branch.
- But they only edit servers scoped to their own branch. Business-wide servers are read-only to them.
- They can't widen scope beyond their branch: the Whole business option is locked, and they can only tick departments inside the branch.
- A Member who opens
/b/<id>/serversgets the Page not found screen. That's deliberate, not a bug.