---
title: "Team templates"
description: "Create reusable workspace templates for teams in OpenWork Cloud"
---

Team templates are the Cloud path for giving a team the same starting workspace setup. Use them when a group should begin with the same skills, MCP config, commands, agents, and provider settings instead of rebuilding those pieces one desktop app at a time.

## When to use templates

- Use a template for repeated team setups, client onboarding, or internal operating systems.
- Use a marketplace plugin (`Settings -> Extensions -> Marketplace` in the desktop app) when you only need to distribute skills or MCPs.
- Use [managed providers](/cloud/share-with-your-team/managed-llm-provider) when the only shared piece is model access.

## Recommended flow

1. Build the workspace locally in the OpenWork desktop app.
2. Add the skills, MCP servers, commands, agents, and providers the team should start with.
3. Share the setup to your OpenWork Cloud organization.
4. Assign the template to the right team.
5. Ask teammates to import the template from `Settings -> Cloud`.

## Keep it maintainable

- Keep secrets out of templates.
- Put shared model credentials in Cloud providers instead of config files.
- Keep reusable skills in a marketplace plugin when several templates need the same skill set.
- Create separate templates for separate teams or client environments.

Team templates are meant to stay boring: one known-good starting point, assigned to the people who need it, imported into the desktop app when they join the workflow.
