Back to docsWho it's for

For teams

Zero for organizations: shared agents and workflows, admin controls, central billing.

Last updated July 30, 2026 · 3 min read

A team workspace gives multiple people in one organization a shared Zero — with shared agents, shared workflows, shared automations, shared connectors, consolidated billing, and centralized controls. It scales from a five-person startup to a five-hundred-person company.

The economics that make Zero work for teams: workflows compound. The first time someone in your org writes a useful workflow, every other member benefits. After a few months, a team that adopted Zero has 30–50 internal workflows capturing how the team actually works — onboarding new hires becomes "here are the workflows you'll use" rather than a wiki.

What teams get

Four capabilities that don't exist in a solo workspace:

  • Shared agents and workflows. Mark an agent public and every workspace member can run it; mark a workflow public and the whole workspace can use it. New hires inherit the team's accumulated procedures on day one.
  • Shared connectors. Authorize Slack once for the workspace; everyone can use it. Same for GitHub, Notion, Linear, and most other team-shared tools. Personal tools (Gmail, personal Apollo) stay per-user.
  • Centralized permissions. Admins decide which connectors are available, which sensitive actions require approval, who can run what. See Permissions.
  • Org-level billing. One credit pool, one invoice, one Stripe customer, one cost-control surface.

Roles

Two default roles:

  • Admin. Manages members, billing, connectors, and security policy. Typically the person who set up the workspace plus 1–2 others.
  • Member. Uses Zero day-to-day. Creates agents and workflows that — when marked public — become available to the whole workspace. Connects personal tools to their own account.

Getting started as a team

A practical rollout path that works for teams of 5–50:

  1. One person sets up the workspace and invites the rest from the Members page.
  2. Admin authorizes shared connectors. Slack, GitHub, Notion, Linear — whichever your team relies on. This is a one-time, one-click step per connector.
  3. Members connect personal tools as they need them. Gmail, personal Apollo, personal Calendar — these stay per-user.
  4. Start with one shared automation. A morning brief that posts to a team channel, or a weekly digest. This shows everyone what Zero can do.
  5. Encourage workflow creation. When someone does the same task twice, prompt them to save it as a public workflow on a shared agent. The team's library grows organically.

Most teams reach "Zero is materially saving time" within 2–4 weeks. The flywheel kicks in once the library hits ~10 workflows.

Sharing agents and workflows

Sharing works on two levels, and both are explicit choices:

  • Agents. Mark an agent public and every workspace member can run it. Keep it private and it stays scoped to its creator — useful for personal automations tied to a personal Gmail or personal CRM seat. A workspace can publish up to 7 org-shared agents; private agents are unlimited.
  • Workflows. Every workflow belongs to exactly one agent and is separately marked public or private. Publishing an agent doesn't publish a teammate's private workflow on it, and a public workflow is only as reachable as the agent hosting it.

Automations can post to a specific channel or DM. Members not in that channel won't see the result.

What's next