Browse docsMenu

Concept

Pod

A self-contained workspace for one team or process — its agents, data, flows, and permissions live together.

What a pod is

Think of a pod as one operating unit of your business: support, hiring, ads reporting. Everything the work needs — AI workers, business data, automations, and access rules — is scoped inside it. Keeping each process in its own pod means agents only see the data they should, and you can share one pod without exposing another.

Reach for it when

  • One team or process needs its own data, workers, and rules.
  • Different processes should not see each other’s data.
  • You want to share a whole working system with someone, not individual pieces.
  • A kit or template needs a clean space to install into.

Create a pod that stays useful

  1. 1
    Name it after the process, not the team — "Support triage", not "Acme Inc".
  2. 2
    Pick one primary unit of work: a ticket, a lead, a claim, an applicant.
  3. 3
    Add the first table for that unit of work before adding agents.
  4. 4
    Invite only the people who run this process; share resources wider later if needed.

Where it lives

The pod switcher sits at the top of the left sidebar. Everything else in this guide lives inside a pod.