Share a team with your staff
Build a team once, export it as a file, and have everyone on your staff import the same bots, skills and routines. Logins never travel.
Murage runs on each person's own computer. To give your whole staff the same team, you build it once, export it, and everyone imports the file. They get the same bots, instructions, skills and routines. Their logins, conversations and memory stay their own.
How it works for a business
- One person builds the team. Set up the bots, write their instructions and team instructions, add skills and routines, and test it on real work.
- Export it. You get a single file.
- Everyone imports it. Each person runs Murage on their own computer and imports the file.
- Each person connects their own accounts. If the team uses Gmail or Slack, everyone signs in to their own. Murage allows up to five labeled accounts per app, such as a personal and a shared support inbox.
- Each person approves their own bots. Imported bots start on Ask, with nothing switched on.
When a draft needs the team's eyes, a bot can post it to a team Slack channel through a connected app, after you approve it.
Export a team
- Choose + in the sidebar, then Export bots….
- Pick a File format:
- ZIP package (.zip): the bots, team relationships, skill instructions, routines and skill files. Use this to share with your staff.
- Markdown (.md): readable bot definitions, skill instructions and routines, without skill files.
- Under Find a bot or team, tick the bots you want, or choose Select team to take a whole team.
- Tick the skill instructions, skill files and routines to include. Skills are never selected for you.
- Choose Preview selection. Murage lists what's in the file, and what's left out.
- Read the review. If there are warnings, tick I reviewed the warnings and want to export this selection.
- Choose Download ZIP package.
What's never in the file
Credentials, conversations, private memory, permission grants and engine sessions are always left out. Connected apps aren't in it either, so each person sets up their own.
Murage scans the export for known secret patterns, such as API keys, and blocks the export if it finds one. The scan checks known patterns only, so read the contents before you share the file.
Import a team
Send the file to your staff the way you'd share any document. Then each person:
- Chooses + in the sidebar, then New Team, then Open a file…, and picks the file.
- Under Import selected package contents, ticks the Bots, Skills, Instructions and Routines to bring in.
- Chooses Preview selection, reads the review, then Import package.
What an imported team looks like
- Every bot gets a fresh identity. Existing bots and permissions stay as they were.
- Skills arrive switched off, and routines arrive paused.
- Connected apps, computer access and the Chief of Staff role are not granted. If the file suggests a Chief, it arrives as an ordinary bot, and your current Chief stays.
- Every bot starts on Ask.
Each person switches on the skills and routines they want, connects their own apps and raises a bot's approval level when they trust it.
Update the team later
Improve the team, export it again, and send the new file. When someone imports a newer version, Murage shows a Package version comparison of what was added, changed or left out since their last import. Importing adds a separate copy, so nothing they changed locally is overwritten.
Good to know
- Everyone needs their own working engine: their own Claude Code or Codex sign-in, their own key, a local model or Flux Router.
- Imported instructions are still text from someone else. Read them before you switch skills on. Skill Guard checks every skill when it's switched on. See Skills, Skill Guard and /learn.
- A shared, always-on workspace for a whole team is planned for Murage Cloud. It isn't open yet.
See also: Backups and export and Teams and team leads.