Back to docsWho it's for

For teams

Zero for organizations: shared skills, admin controls, central billing.

Last updated May 27, 2026 · 3 min read

A team workspace gives multiple people in one organization a shared Zero — with shared agents, shared skills, shared schedules, 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: skills compound. The first time someone in your org writes a useful skill, every other member benefits. After a few months, a team that adopted Zero has 30–50 internal skills capturing how the team actually works — onboarding new hires becomes "here are the skills you'll use" rather than a wiki.

What teams get

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

  • Shared agents and skills. When an agent is marked public, every workspace member can run it — along with the skills attached to it. New hires inherit the team's accumulated workflows 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 skills 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 schedule. A morning brief that posts to a team channel, or a weekly digest. This shows everyone what Zero can do.
  5. Encourage skill creation. When someone does the same task twice, prompt them to save it as a skill on a public agent. The team's skill library grows organically.

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

Sharing agents and skills

Sharing happens at the agent level. Mark an agent as public and every workspace member can run it, along with the skills attached to it. Keep an agent private and it stays scoped to its creator — useful for personal automations tied to a personal Gmail or personal Apollo.

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

What's next