DocumentationSkills for enterprise AI
Distribute skills in the team
In anymize an admin can give skills to the whole team or to a group, either as an offer or as required for everyone.
3 Min
Why distribute centrally at all?
Because otherwise the result depends on who is asking. If your client letters should always have the same structure, if every council briefing needs the same outline, or if no text may sound like AI, then that rule does not belong in people’s heads - it belongs in a skill everyone has.
- Everyone works with the same flow, including new colleagues on day one.
- A change to the house convention is made once and applies immediately for everyone.
- Distributed skills do not count against members’ personal skill limit.
How does it work?
The principle is quickly told. An admin picks a skill from their own stock in the Governance Center, chooses the scope and decides with a switch how binding it is.
| Setting | What the member notices |
|---|---|
| Optional | The skill appears for members as installable. Anyone who needs it activates it themselves. |
| Always on | The skill runs in every chat and project. For the member it appears as active and locked; it cannot be turned off or removed. |
As scope you can choose the whole team or a single group, for example only the council secretariat, only HR or only the department running a tender.
If a colleague asks why they cannot turn a skill off: it is required by the team. That is not a fault, it is the “Always on” setting. The skill card carries the note.
What is not settled here
This page only describes the principle. Where the switches sit, who may operate them, how groups are created and what else can be set centrally - for example allowed models or connectors - is in the Governance Center chapter.
One point still belongs here: what is shared is the instruction, not the case. A skill contains the method, no client or citizen data. And what happens in members’ individual chats stays with them, even if the skill comes from the house.