Most of the band doesn't need a dashboard login — they interact with BandBrain over SMS / email. But sometimes you want a co-admin (a manager, a label rep) to be able to see the dashboard, manage roster, send comms.
Sending a dashboard invite
- Go to Roster
- Find the person's row (in any section)
- Click to expand the edit panel
- Confirm they have an email set on the row
- Click invite to dashboard
What happens next
- BandBrain sends them a Clerk organization invitation email
- They click the link → land on a "JOIN THE BAND — Set a password to accept" page
- They set a password → land in your org's dashboard
- Their roster row shows an ADMIN chip
The invitation auto-binds them to your org. They don't see a "create your own org" prompt.
Merging with existing data
If someone you're inviting already has data in your roster (you added them via SMS first, then later decided to invite to the dashboard), BandBrain automatically merges:
- Their Clerk login attaches to the existing roster row
- Their pre-existing role / category permissions / channel mappings stay intact
- No duplicate "person" rows in the database
The merge happens transparently — no clicks needed.
They already have a BandBrain login
If the person signed up for BandBrain on their own before you added them, you don't need to send an invite. When you add them to the roster (or set their email on an existing row, or click invite to dashboard) with the email they signed up with, BandBrain:
- Links the roster row to their existing login (one person, not two)
- Keeps the role and permissions you set
- Adds your band to their dashboard right away. Next time they sign in, they're in your band instead of being asked to add one.
Revoking or resending
If you sent an invite and want to revoke or resend:
- The Management & Admins section shows pending invites at the bottom
- Click revoke to cancel, or just send another invite to the same email
Edge case: they accept with a different email
If you invite matt@band.com but Matt uses matt@gmail.com for his Clerk signup, the merge fails and you'll end up with two roster rows — one with the original phone/email, one for the new Clerk user. Resolve manually by editing the duplicates.