Team and roles

A workspace is shared by a team. Each member has one role, and the role means the same thing everywhere in the app. Manage members under Settings → Members.

• Owner — everything an editor can do, plus members, invites, API keys and lending stages.
• Editor — creates content and operates the live desk.
• Operator — runs the screens: Live, Backstage, take, release, blackout and GO. Reads stories and presets by name and edits nothing. The menu shows an operator only what they can use.
• Viewer — reads everything, changes nothing.

What each role may do with screens and releases:

• Publishing — editors and owners publish, roll back and hold stages. Operators run what is published and publish nothing.
• Devices — operators can identify a screen, take a screenshot and Watch live in their venues. Changing a screen’s settings, restarting, moving or unpairing it needs an editor or the owner. See Remote settings and actions.
• Casts — operators accept, cut and mute casts on the Live board, in their venues.
• Renderers, player links, agent keys — owners upload and activate renderers and revoke all player links; everyone makes their own agent keys, which can never do more than their role. See AI agents.

An invite is a link with the role already on it. It works once and expires, so a forwarded link is not a standing door.

With more than one venue, an operator gets a Venues button next to their role: tick the venues whose screens they may move. None ticked means every venue. A screen outside their venues stays on their desk, locked, with a sentence saying why.

A loan hands some of your stages to another workspace for a window — an event company running your hall for a day. The screens stay yours: same player link, same devices. Inside the window their show plays; outside it, yours.

During the window your desk shows the stages locked — Lent to … until 18:00 — and both call sheets draw the loan as a striped band. Your bookings under it wait. At the end the screens go back to your call sheet by themselves, within seconds. Revoke now ends a loan early; both sides’ history says who did it.

When the guest is one person — an event’s stage manager — use Invite a guest operator… on Venue → Stages instead. They run the stages you pick, for the window you set, from your Live board and Backstage, and see nothing else of yours. Their access ends by itself; you find them under Guest operators in the member list, where you can end it early.

To rehearse an event without touching the real one, an owner opens Settings → Workspace → Duplicate workspace…, looks at what will be copied, and presses Copy. The copy is a new workspace you own, with the venues, rooms, stages, scenes, stories, collections, presenters, sessions, shows, engagements, media and releases of the original, every link between them pointing into the copy — so a test run there plays the same program on the same kind of stages. Screens, members, invites, presenter links, API keys and what guests posted stay with the original, and rooms and engagements get new QR codes: pair a spare screen to the copy’s stages and make fresh presenter links there. The original is only read, never changed. The copy never emails real people: every email address in it becomes speaker-name@ a domain you choose, or is left empty.