New: Bring Your Whole Team Into Quadraviz
Your scenes, animations and channels now belong to an organisation instead of one login. Invite your designer, your operator and your client, and give each of them exactly as much control as they need.
Team Quadraviz
August 23, 2026 · 5 min read
Until now, everything you built in Quadraviz belonged to one account. Which was fine right up until the moment a real production needed to touch it — and then it wasn't, because real productions are not one person.
A designer builds the scene. An operator runs it on the night. A producer wants to look without touching anything. Someone has to hand the laptop over, or share a password, or export and re-import.
That's fixed. Everything now belongs to an organisation, and people are invited into it.
What changed
Scenes, animations, resources, collections and channels belong to your organisation rather than to you. Everyone in it sees the same library and works on the same shows.
If you work alone, nothing about your day changes. You already have a personal organisation — we made it when you signed up — and it holds everything you have built so far. The only visible difference is a label in the header telling you which one you're in.
That label is there deliberately, even with one organisation. What's on your screen belongs to somebody, and leaving that implicit is exactly how a freelancer edits the wrong client's scoreboard.
Four roles
Not everyone in a production should be able to delete a collection.
| 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 and manage keys. |
| Owner | Everything above, plus billing. |
Operator is the one we'd point at. It's for the person driving the show and nobody else: a freelance camera op running your scoreboard for one weekend can hit every button in the controller and cannot delete a single thing.
That's not about trust. It's that a role which cannot delete a collection is a role that cannot delete a collection at 3 minutes to air, by accident, while looking for something else.
Two rules the platform holds for you, so you don't have to remember them:
- Nobody hands out authority they don't hold. An admin can invite admins, never owners.
- The last owner can't be removed or demoted. There is always someone who can pay the bill and let people in.
Inviting people
Settings → Organisation → Invite someone. Type an address, pick a role, send.
They get an email naming your organisation, the role, and who invited them, with a button that takes them in. If they don't have an account yet, the link takes them through sign-up first and drops them into your organisation afterwards.
Nobody loses what they already had. Joining your organisation adds it to their account — it doesn't replace their own, and they switch between them from the header.
A few things we decided on purpose:
Invitations expire after seven days. An invitation sitting in an inbox is a standing way into your organisation. One that never expires is a standing way in that nobody remembers giving out.
A link works once. Once used, it's spent. A forwarded email is not a second seat.
It only works for the address you sent it to. The accepting account has to use that email, and that email has to be confirmed. Forwarding an invitation to a colleague does not let them in — which is the point. It's what makes an emailed link safe to send at all.
Sent one to the wrong address? Pending invitations are listed under Waiting to be accepted. Hit Withdraw and the link is dead. We can't un-send the email, but we can make it useless.
Why we did this now
Honestly: because of what people were doing without it.
Shared logins. A production Discord with a password pinned in it. One person who couldn't go to lunch during a tournament because they were the only one who could reach the graphics.
Every one of those is a workaround for missing multi-user support, and every one of them is worse than what we've built. Shared credentials can't be revoked for one person. A pinned password doesn't expire. And "the only one with access" is a single point of failure with a lunch break.
There's a second reason. Organisation ownership is what made API keys possible. A key that belongs to a person dies when that person leaves — which is fine for a script and disastrous for a panel bolted into a rack. Keys now belong to the organisation, so installed hardware keeps working after the person who set it up has moved on.
Getting started
- Rename your organisation. Settings → Organisation. "Northlight Broadcast" reads better in an invitation than whatever your personal account got called.
- Invite one person at the role you actually want them to have, not the highest one.
- Check the header so you know which organisation you're in before you start editing.
The docs go deeper on both: organisations and roles, and inviting your team.
If you're already running shows with a shared login — this is the week to stop.