Team
Organisations and roles
TL;DR — Your scenes, animations, resources and channels belong to an organisation. Everyone in it sees the same content. Roles decide what each person can change.
What an organisation is
An organisation owns your work. Scenes, animations, resources, collections, channels and API keys all sit inside one.
When you signed up, we made you a personal organisation automatically. If you work alone, that is the only one you will ever see, and nothing about it gets in your way.
The moment a second person joins, the organisation stops being an implementation detail and starts being the useful part: everyone works on the same library instead of emailing files around.
Who can do what
Four roles, weakest to strongest. Each one includes everything below it.
| Role | Can |
|---|---|
| Operator | Run a show — play scenes, fire triggers, change values on air. Cannot change what exists. |
| Member | Everything above, plus build scenes, animations, collections and resources. |
| Admin | Everything above, plus invite people, change roles, and manage API keys and webhooks. |
| Owner | Everything above, plus billing, and deleting the organisation. |
Two rules the platform enforces for you:
- Nobody can hand out authority they do not hold. An admin can invite members and other admins, never owners.
- The last owner cannot be removed or demoted. An organisation always has someone who can pay the bill and let people in.
Knowing which one you are in
The organisation you are working in is always shown in the header, next to your account. It is shown even when you only belong to one — what is on screen belongs to someone, and leaving that implicit is how people edit the wrong client's graphics.
If you belong to more than one, that indicator becomes a switcher. Pick another organisation and the dashboard reloads into it.
Switching is a hard boundary, not a filter. While you are in one organisation you cannot see, query, or control anything in another — not through the dashboard, not through the API.
Rename your organisation
Settings → Organisation → Name. Admins and owners only.
Worth doing early if you are working with clients: "Northlight Broadcast" reads better in an invitation email than the name your personal account was created with.
Next steps
- Invite your team — Bring people in
- API keys — Let a control surface drive your channels