Running Murage for a business with staff
How a business with staff runs Murage today: one install per person, a shared team package, Slack drafts with approval, labeled accounts and naming conventions.
Murage is built for one person at their own computer. A business with staff runs it the same way, many times over: each person has their own install, and everyone works from the same team definition. This page covers how to set that up well.
The model: one install per person
Each person installs Murage on their own computer and runs their own bots. That means:
- Each person's conversations, memory and files stay on their computer.
- Each person signs in to their own engine: their own Claude Code or Codex sign-in, their own key, a local model, or Flux Router.
- Each person connects their own apps and approves their own bots.
- Logins never travel between people.
A shared, always-on workspace for a whole team is planned for Murage Cloud, which isn't open yet. Until then, remember that each person's routines only run while their own computer is on and Murage is running.
Build the team once
Pick one person to own the team definition, usually whoever knows the process best.
- Build the team in their Murage: bots, instructions, skills, channels and routines.
- Write the House Rules and team brief the business wants everyone to use.
- Use it on real work for a week and fix what's off.
- Export it: + → Export bots…, pick ZIP package (.zip), Select team, tick the skills and routines, Preview selection, and download.
Keep the exported file somewhere shared, such as a company drive, with the release number in the file name.
Everyone imports it
Each person chooses + → New Team → Open a file…, picks the file, ticks what to bring in, previews and chooses Import package. Imported bots start on Ask, with skills switched off and routines paused. Each person then:
- connects their own apps;
- switches on the skills and routines they want;
- raises approval levels for bots they've come to trust.
House Rules aren't part of a team export. Share them as a text file, and have each person paste them into Settings → House rules.
Updating the team
When the owner improves the team, they export it again with a higher release number and share the new file. When someone imports it, Murage shows a Package version comparison of what was added, changed or left out. The import adds a new copy rather than overwriting anything that person changed, so ask people to archive the old bots once the new ones are working.
For the format itself, see Team packages.
Working together through Slack
Bots can post to your team's Slack channels through Slack as a connected app. A good pattern:
- Create a channel such as
#bot-drafts. - Give one bot per person access to Slack, and add a House Rule: "Post drafts for the team in #bot-drafts, never in client channels."
- Posts go through your approvals like any other action. Keep the posting bot on Ask until you're happy with its drafts, and don't use Always allow on Slack's posting tool, because that covers the whole tool.
This is separate from messaging your own Chief of Staff from a Slack direct message, which is covered in Channels.
Shared inboxes and several accounts
Each app can hold up to five labeled accounts. That covers a common setup: your own mailbox plus a shared one, such as "Me" and "Support". Label each account clearly, because bots and approval cards refer to accounts by their label. Each person signs in to the accounts they're allowed to use, on their own computer.
Naming conventions that help
With several people running the same team, clear names save confusion.
- Bots: keep the name plus a role, such as "Mira (Brand)". The role tells people what a bot is for when it turns up in a card, a channel or a Slack post.
- Signatures: add a House Rule for how bots sign Slack posts and emails, such as "Drafted by Mira for Alex". It makes clear who a bot works for.
- Channels: name channels after the job ("Weekly pipeline"), not the people in them.
- Routines: start with the cadence: "Mon 9am pipeline review", "Daily 8am inbox sort".
- Accounts: label connected accounts by what they are ("Support inbox"), not by a person's name.
- Packages: put the release in the file name, such as
sales-team-1.3.0.zip.
Security for a team
- Each person approves their own bots, so each person is responsible for their own approval levels. Agree a company default, such as "Ask for anything customer-facing, Full access only for research bots".
- Keep finance and payment work with one person, on Ask.
- Nobody should share API keys or sign-in files. Everyone gets their own.
- Read imported instructions before switching skills on, even from a colleague. Skill Guard checks every skill, but it only knows patterns.
What's not available yet
- No shared workspace: bots, memory and conversations don't sync between people.
- No central admin console or company-wide policies.
- Routines don't run when a person's computer is off.
These are the jobs Murage Cloud is meant for, once it opens.