Organizations & access
An organization is your tenancy and access boundary in BitsWeave. You and your agents authenticate to it with a Personal Access Token.
An organization is the boundary around everything in BitsWeave. Your projects, tasks, work sessions, notes, decisions, and connected tools all belong to exactly one organization — and nothing crosses that line. It's your tenancy boundary and your access boundary at the same time.
What lives in an organization
Everything you do in BitsWeave happens inside an organization:
- Members and roles — the people in your organization, and what each one is allowed to do.
- Projects and tasks — the work itself, organized for the whole team.
- Work sessions — the live record of who's doing what, including the sessions af-tap mirrors from your machine.
- Connected tools — the GitHub, email, and other integrations your agents reach through the MCP surface.
Two organizations never see each other's data. When you invite a teammate or add an agent, you're adding them to your organization — and that membership is what grants access.
Authenticating
Interactive agents (Claude Code, Cursor, …) sign in to the MCP surface over OAuth — there's no token to paste; see Connect your agents.
Headless access uses a Personal Access Token (PAT) — a credential (prefixed
aft_) minted under your account and organization:
- af-tap authenticates with a PAT. The af-tap-install skill mints one for you over MCP and writes it into af-tap's config.
- Scripts and CI can hold a PAT to call the API directly.
Mint and revoke PATs at
/app/account/tokens, or
over MCP with organization.tokens.create. A PAT carries the access of the
organization and role it was minted under, so a token can never do more than
its owner can. Tokens can be listed and revoked at any time — revoke one and
anything using it loses access immediately.
Treat a PAT like a password
A Personal Access Token grants access to your organization. Store it securely, never commit it to source control, and revoke it the moment you suspect it's leaked.
Where this fits
The organization is the boundary; your OAuth session or PAT is the key. With both in place, your work sessions and your agents' MCP calls all land in the right place, scoped to the right people.
To create an organization and connect your first agent, follow Getting Started.
The MCP surface
Add BitsWeave's MCP server to your agent and it gains one audited interface for organizations, projects, tasks, sessions, and your connected tools.
Brokers
Brokers wire BitsWeave to your external tools — GitHub, SonarQube, Grafana, email — so events flow in and your agents act back out.