teams + roles.
yala is built for the artist who’s their own manager, but plenty of you have help. when you do, every workspace has four roles + an invite flow. shared keys are bad keys.
the four roles.
- owner — the founder. one per workspace. can do everything including delete the workspace, change billing, transfer ownership.
- admin — the manager / label-services lead. can invite + remove members, change roles (except owner), change pixels, change domains, archive the workspace.
- editor — the day-to-day operator. can make, edit, publish, archive links. can write broadcasts. can’t touch members or billing.
- viewer — read-only. see everything, change nothing. handy for the publicist who wants the dashboard but not the keys.
inviting someone.
- go to workspace → members.
- click + invite, enter email + role.
- they get an email with a deep-link. they create an account (or sign in) and land directly in your workspace at the assigned role.
- invites expire in 14 days, are revocable any time before accepted, and are bound to the email — they can’t be forwarded to a different account.
changing a role / removing.
on the members list, hit the role dropdown for any member to change. removing instantly de-authorizes them; their session is invalidated within minutes via the supabase JWT-rotation flow.
audit log.
every workspace records: member added/removed, role changed, link published/archived, broadcast sent, domain added, api-key created. visible in members → audit on teams + enterprise tiers.
multiple workspaces.
the teams tier ships with 10 workspaces; enterprise unlimited. each workspace is fully isolated — different domains, different links, different members, different pixels. you can be a member of as many workspaces as you want; the top-center dropdown lets you switch between them.