Skip to content

Project

A Project is the logical grouping for related Agents.

One layer below Org, one layer above individual Agents. Examples: "EU customer support", "Finance refund automation", "Internal data agents".

Lives withinone Org
Owned byone or more Teams (with role membership in each)
Containsone or more Agents
Has its ownPolicy floor (the project level of the cascade)

A Project bundles related Agents under a shared Policy floor. The Project's project admin (a Team role) authors that floor. Every Agent inside the Project inherits it; agent-level overrides can tighten further but never loosen.

Why projects exist:

  • Different Agents have different needs. A customer-support Agent and a finance-refund Agent shouldn't share the same fine-grained rules.
  • But many Agents share a domain. Five customer-support Agents probably want the same baseline (allow gmail.send, deny pii_archive, EU AI Act + GDPR packs applied).

The Project carries that shared baseline. Each Agent within it just adjusts at the margins.

Org
│ org-level Policy floor (compliance baselines, forbidden capabilities)
Project A Project B …
│ │
│ project-level Policy │ project-level Policy
│ floor (project domain │ floor (project domain
│ rules) │ rules)
▼ ▼
Agent 1 Agent 2 … Agent 1 …
│ per-agent overrides
│ (typical-session shape, specific tool constraints)
one or more Sandboxes per Agent
PersonaSurfaceWhat you do
Org adminDashboard / tappass project createCreate projects; assign owning Teams
Project adminDashboard / tappass policy apply --level project=<id>Author project-level Policy floor
AuditorDashboard audit viewsSee per-project audit (limited to projects they have rights to)