Share a scene with a client

Who can share

Anyone who can edit the project: a collab seat plus a role that edits. They can create the link, invite people, let guests in and present. An administrator without a seat cannot. A locked scene can still be shared — it is usually the one you want to show.

Create the link

Open Share with client and press Create link. There is one link per scene, and it can be used again and again. Creating a new one revokes the old one, so there is never more than one live.

Let invited guests in automatically is on by default. It applies to addresses on your guest list only — see below. You can change it later in the same dialog.

The link expires after 14 days. Revoke link kills it at once: everyone watching is told, and the presentation stops in every tab and on every machine where you have the scene open. Expiry does the same within a minute of the link running out.

Invite people

Type an address under Invite by email and press Invite. Each address gets a mail with the link. The list is who you expect:

• With Let invited guests in automatically on, somebody on the list confirms their address by email and is straight in — whether you are there or not. They look around the latest released version.

• Nobody comes in on their own until the scene has a released version. Until then invited guests wait at the door like everybody else, and the dialog says so. See Release a version.

• Switching it off makes everybody wait for you again. It does not remove anybody already watching.

• Withdraw takes somebody off the list — and out of the session, if they are waiting or watching.

The waiting room

Everyone who opens the link types a name and an email address and confirms it from a mail. Only then are they at your door, with the confirmed address beside their name. Nobody reaches the waiting room anonymously.

A knock reaches you with Share closed: a small prompt lets you admit or turn away the guest without reopening the dialog. Dismissing the prompt leaves them waiting; it does not refuse them.

Your choices for somebody waiting:

• Let in — for now. The next time that person comes, they wait for you again.

• Until … — invited guests only. They come straight back in on their own, each time they confirm their address, until the link expires. For a client who wants to look again later without booking a meeting. It needs a released version.

• Turn away — they are not admitted.

If nobody who can let them in has the scene open, the project lead gets an email (or whoever created the project, or the organisation's owners) — at most one every 15 minutes per link, however many people are waiting. So do not leave a waiting room unattended.

Who is watching

Share with client lists your guests under the invitations, with Let in, Until …, Turn away and Remove next to them:

• Waiting — at the door.

• Watching — in, with the viewer open right now. The count comes from the live connection.

• Admitted · offline — let in, but the viewer is not open at the moment.

• Away · place released — their tab has been in the background for 10 minutes, so their place went to somebody else. Coming back takes a place again if one is free.

• came in on their own — an invited guest looking at the released version, not your work in progress.

• Not invited — the address is not on your list. Usually a forwarded link.

Remove ends a guest's access. It is not a ban: with the link they can confirm their address and knock again, but need your approval again. Removing someone takes a second, and everyone else's view blinks — they are moved to a new private session and the removed guest is left behind on the old one.

Removing or turning away an invited guest also stops them coming in on their own; otherwise confirming their address again would walk straight back in. Their invitation then shows asks first, and Allow in lets them come in on their own again. To keep somebody out altogether, Withdraw their invitation.

When the room is full

A room holds a limited number of people watching at once. When it is full, the dialog says so and Let in is unavailable until somebody leaves. Anyone who knocks meanwhile stays at the door, so you can remove someone and let them in. An invited guest who would come in on their own is told at the door that the room is full.

The limit keeps the server responsive mid-show; it is not something you buy or run out of. Your own upload does not grow with the audience. If you expect a genuinely large audience, support can raise it for one link, for a set period.

Presenting

• The view is sent from your browser tab. Close the tab and the presentation stops. Leave it in the background and it slows to about one update a second — keep it in front while you present.

• Guests start by following your camera, and they choose Live or Plan themselves. Once they pick one, it sticks: Follow host then follows your camera within their choice. A client may not be looking at the same mode you are.

• They see your edits a couple of seconds after they are saved — the rig as stored, not your unsaved changes. Guests who came in on their own see the released version instead.

• Their header says where the light comes from: Live DMX while your console drives the rig, Preview levels otherwise. When live DMX stops mid-session they are told — Live DMX stopped · preview levels — so a changed look is not mistaken for a decision.

• Saved views you offer appear in their Views… menu. In your Views list, the share icon next to a view offers it to guests; views you did not offer are not sent at all.

• Saved looks appear in their lighting menu. Recalling one is a preview on their screen only.

What guests see — and do not

• The same rig you do, scenery included: fixtures, truss, and any venue, stage or set imported from an MVR.

• ⚠ Your patch. Addresses, universes and fixture names go with the scene, because that is what lets the rig light up from live values. If the patch is not something a client should have, do not share the scene.

• Not each other. You see the guest list; guests do not see each other's names.

• No Problems panel, no settings, no patch panel, and nothing they do changes your scene or your camera.

Comments from clients

Clients comment only if you let them. Each invited address has a Comments switch, off by default. A client switched on can pin a comment on a light, a truss, a spot in the room or the whole scene, and it reaches your Comments column at once, marked (client). Switching it off takes effect immediately. Somebody who came in on a forwarded link can never comment.

Every thread is Private or Public, and private is the default. Private: the writer and your team. Public: also every client shown this scene. Making a thread public shows everything already in it, replies included, so it asks first. Making it private again cannot unsay what clients have read.

What your client sees of all this is on What your client sees — a page you can send them.