Why sharing the setup rarely works
You can send a teammate your skills and a guide. Then they need a terminal, a login, your MCP servers and your context, and it stops working the first week. The flow stays with you.
Share the agent, not the setup
Your agent already has all of that. Connect it to a channel, name its role and let your team mention it. At ACME, the founder's agent drafts sales follow-ups, and the sales lead asks for them in #sales.

Turn a flow into a hosted agent
When a flow is worth keeping, give it its own agent on its own computer in Laze, with a role and instructions. It keeps running when you log off, and on a schedule if you want.
Stay in charge
You decide who can reach your agent. When a teammate's request needs one of your keys, the approval comes to you, so they can use the flow without holding the keys.
Keep your chat
Each person can link their Slack, and channels show up in Laze with messages syncing both ways. Your team does not have to move to get this.
