Join or create an organization
An organization is your tenancy and access boundary in BitsWeave. Join one you've been invited to, or create your own — then pin it as your active org.
Everything in BitsWeave lives inside an organization — your projects, tasks, work sessions, tokens, and connected tools all belong to exactly one org, and nothing crosses that line. Before you connect an agent you need to be in an org and have it pinned as your active one. There are two ways to get there: join an org someone invited you to, or create your own.
Why this comes first
Your Personal Access Token and your work sessions belong to your membership in a specific org. If you connect an agent before you're in the right org, its sessions and tool calls land in the wrong place. See Organizations & access for the full model.
Sign in first
Open your BitsWeave instance and sign in. BitsWeave supports email + password as well as GitHub, Google, and passkey sign-in.
After signing in you land on the organization picker at /orgs. It lists
every org you're a member of plus any pending invitations, and — if your
account is active — an entry point to create a new org.
Option A — join an org you were invited to
If a teammate invited you, the invitation shows up two places:
- In the email you were sent — the link carries the one-time invite token.
- On the
/orgspicker, under pending invitations (org name, role, and who invited you).
To accept, open the link from the invitation email. The picker lists pending
invitations for visibility, but accepting needs the token from the emailed link
— there's no in-place "accept" button on /orgs. Once accepted, the org appears
in your membership list on /orgs.
No invitation yet?
Ask whoever runs your instance (or an admin of the org you want to join) to invite you. They create the invitation from the org's members settings; you'll get an email with the accept link.
Option B — create your own org
If you'd rather start fresh, create an org from the picker. Creating an org is an
active-account affordance — if your account is still waitlisted, the create
entry is hidden and /orgs/new bounces you back to /orgs.
Open the create form
From /orgs, choose to create a new organization, or go straight there:
Name it
Enter a name (e.g. Acme Corp). A URL-safe slug auto-derives from the
name as you type (acme-corp) and stays editable — slugs are lowercase letters,
numbers, and hyphens only. If the slug is already taken, the form surfaces the
error and keeps what you entered so you can adjust it.
Create
Submit the form. You become the new org's first admin, the session is
auto-pinned to it, and you land in the app at /app with that org active —
no extra step to select it.
Switching your active org
If you belong to more than one org, the one you're "in" right now is your
active org — pinned to your session. Switch it from the /orgs picker: pick
an org and you're re-pinned to it, then dropped back into the app with that org's
data resolved server-side.
The active org matters everywhere downstream: it's the org your
connected agent acts in (the
x-active-org header), and the org your
context explorer reads from.
Next
With an org joined or created and pinned active, you're ready to connect your agents.
Onboarding
A short, hands-on path from zero to a connected agent — join or create an org, connect your existing AI agents, then explore the context they build.
Connect your agents
Connect the AI agents you already run to BitsWeave in three steps — add the MCP server over OAuth, install af-tap with the af-tap-install skill, then verify by creating an artifact and watching a live session.