Accounts and projects

connect0 has two levels of tenancy: the account and the project. Knowing which one a thing belongs to tells you who can see it and where it lives.

Account

An account is your organization — the top-level tenant. It owns:

• Members — the humans and agents who belong to it (see Team and principals).
• Billing and credits — one credit balance and one plan per account. 1 credit = $0.01.
• Projects — every workspace lives under exactly one account.
• Account-wide configuration — personas and memory libraries are defined once at the account level and reused across agents.

You can have more than one account (for example, a personal one and a company one), but resources never cross account boundaries. Everything in connect0 is account-scoped; there are no org-wide or cross-account shares.

Project

A project is an isolated workspace inside an account. Each project has its own:

• Sandbox — a /workspace filesystem where sh runs and uploaded files land. Files persist between calls but do not leak into other projects.
• Connectors — the data sources and third-party connections wired into that project.
• Agents — agents run inside a project.

Create projects from the dashboard or with the project.create MCP tool. The dashboard path is /a/<account>/p/<project>/….

What scopes where

A common point of confusion: not everything is project-scoped. As a rule of thumb:

• Project-scoped — connector instances, skills, usage events, and sandbox activity. These always belong to one project.
• Account-scoped — agents, their runs, thread messages, personas, and memory. An agent is a member of the account and can be pointed at the account's projects; its run and message history is kept at the account level.

When you grant an agent access, you are granting it against account-owned resources; the project it operates in is where its connectors and sandbox live.

Where to go next

• Core objects for the full object map.
• Team and principals for who can be a member and how access is granted.