Managing multiple bands

If you tour-manage (or otherwise admin) multiple bands, each gets its own BandBrain organization. Switching between them is one click.

How it works

Each org = one band's BandBrain workspace. Fully isolated:

Separate roster
Separate knowledge base
Separate connectors (each band connects their own Drive / Stripe / Square)
Separate SMS number
Separate email alias

You can be a Clerk org member of multiple orgs at once. Each org has its own permissions.

Switching

Top-right of the dashboard, there's an org switcher (band name + dropdown chevron). Click it to see all orgs you're a member of. Click any to switch context.

After switching:

The whole dashboard now reflects that band's data
The SMS / email aliases change
The roster, knowledge, comms history all show that band

URL stays the same — the org context is per-session.

Identity across orgs

Your identity (memory, preferences) is per-org. If you've told the agent "I like tea, not coffee" for Band A, that's specific to Band A's tenant.

This is by design: a memory you set up for one band shouldn't leak to another, even if you're the same human.

Creating a new band

In the org switcher, look for "Create organization". Pick a name (usually the band's), and you're in a fresh workspace.

You'll need to do the first five minutes setup for each new band.

SMS number per band

Each band has its own dedicated Twilio number. When you (the TM) text that number, the agent treats you as the TM for THAT band — uses their data, their permissions, their context.

If you forget which number is which, the Channels page shows the number for the current org.

Email aliases per band

Each band gets a unique <bandname>@bandbrain.ai. Sending the same content to two different aliases ingests separately into each band's knowledge base.

Tip: name the aliases distinctively (e.g. "northernlights" and "sideproject") so you don't accidentally forward a venue contract to the wrong band.

Billing