Template Management
Build, categorize, import, and export reusable workspace templates.
Platform administrators manage the global template library from Admin > Templates. Templates are available to every workspace, while only platform administrators can change them.
Template structure
The library has three composition levels:
- A workspace template selects default template groups.
- A template group packages one business capability and may include agent, team, and skill templates.
- Resource templates create agents, teams, and skills. Agent templates can include skills. Team templates include agent members and exactly one leader; skills are assigned through agent templates.
Categories such as Engineering, Operations, or Finance apply to every template type and are included in exports. A skill's own category remains separate from its template-library category.
Each non-skill template also has an administrator-only internal description. User-facing names, descriptions, and instructions are maintained per locale in the template translations and are all available in the administrator editor.
Skill requests
Workspace members with skill write access can request a workspace skill as a global template from the skill row menu. They provide a template key and a reason. The skill page shows the latest request status and any administrator decision note.
Platform administrators review submissions in Admin > Templates > Skill requests. The queue shows the source workspace, skill, requested key, and reason, and allows previewing the skill content. Approval creates a skill template from the current skill contents and files. Rejection requires a reason, which the requester can see on the skill page.
Import and export
Exporting a template produces a ZIP bundle containing the selected root, all recursive dependencies, categories, relations, and complete skill file trees. Import first validates the archive and shows a preview.
When a skill template name conflicts, choose Skip, Overwrite, or Rename. Other template types are renamed automatically. Existing categories are reused by case-insensitive name and their target-system details are preserved. A confirmed import is transactional: validation or write failure leaves the template library unchanged.
Templates never contain runtime bindings, environment variables, runtime configuration, MCP configuration, or custom runtime arguments.