Present a scene to a client
One link per scene, a guest list and a waiting room you control. Nobody sees anything of the scene, not the rig and not the name of the show, until they are let in.
Who can present
Owners and managers of a project can present: create the link, invite people, let guests in and lead the meeting. A planner prepares the scene but does not host.
Presenting needs no collab seat. It never changes the scene, so an owner without a seat can still present.
A released, locked scene can still be presented. It is usually the one you want to show.
Opening the Present workspace
The Present workspace holds everything a meeting needs: the waiting room on the left, the looks on the right and comments under the viewport. Press 5 to open it.
File › Share with client… opens the same controls as a dialog, for when you would rather stay in another workspace.
Creating the link
Each scene has one link. Create link makes it, and it can be used again and again. Creating a new one revokes the old one, so there is never more than one live.
The link expires after 14 days, and the date stands under it.
Revoke link ends the link 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.
Inviting people
The guest list names the people you expect. Type an address under Invite by email and press Invite. Each address gets a mail with the link.
Comments beside an address decides whether that person may comment. It is off until you tick it, and switching it off takes effect at once.
Invited guests can come in on their own while Let invited guests in automatically is ticked. They confirm their address by email and are straight in, whether you are there or not, and they look around the latest released version.
That needs a released version. Until the scene has one, invited guests wait at the door like everyone else, and the waiting room says so. See Release a version.
Withdraw takes somebody off the list, and out of the session if they are waiting or watching.
Letting guests in
Every guest confirms an address before knocking. Only then do they reach your door, with the confirmed address beside their name. Nobody reaches the waiting room anonymously.
Three answers wait for a knocking guest:
Let in, for now. The next time that person comes, they wait for you again.
Until …, for invited guests only. They come back in on their own each time they confirm their address, until the link expires. It needs a released version.
Turn away. They are not admitted.
A prompt announces knocks while the waiting room is not on screen, so you can admit a guest from Rig or Focus. Dismissing the prompt leaves them waiting.
An unattended door sends an email. If nobody who can let guests in has the scene open, the project lead hears about it, at most once every 15 minutes per link. Do not rely on it during a meeting.
Who is watching
The guest list under the invitations shows each guest's state:
Waiting: at the door.
Watching: in, with the viewer open right now.
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.
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, and they need your approval again. Removing an invited guest also stops them coming in on their own. Their invitation then reads asks first, and Allow in restores it.
When there is no room
Presentation seats belong to the organisation. Every guest watching, with you or on their own, takes one, across all presentations of the organisation at once. When they are all in use, the waiting room says: All 5 presentation seats of your organisation are in use, across all its presentations. Let somebody go to make space.
Each presentation also has a safety limit, which keeps the server responsive mid-show. It reads: This room is at its limit of … people watching at once. Let somebody go to make space, or ask support if you are expecting a bigger audience. Support can raise it for one link, for a set period.
In both cases Let in waits until somebody leaves. Anyone who knocks meanwhile stays at the door, so you can remove someone and let them in.
Leading the meeting
Your browser tab sends the view. Close the tab and the presentation stops. Leave it in the background and it slows to about one update a second, so keep it in front while you present.
Guests follow your camera and your looks. A guest who drags the view takes their own camera; Follow host brings them back.
Guests choose Live or Plan themselves. A client may not be looking at the same mode you are.
Saved edits reach guests after a few seconds. They see the rig as stored, not what you are still dragging. Guests who came in on their own see the released version instead.
The guest header names the light source: Live DMX while your console drives the rig, Preview levels otherwise. When live DMX stops mid-session they read Live DMX stopped · preview levels, so a changed look is not mistaken for a decision.
Guests see the views you offer. In your Views list, the share icon beside a view offers it to guests; views you did not offer are not sent.
Guests pick looks from pictures. The looks bar along the bottom of their viewer shows each saved look with its picture. Picking one is a preview on their screen only.
Guests see no camera symbols. IMAG cameras are an editor's aid, so the viewer starts without them, and the screens show their picture as in the editor.
What guests see, and what they do not
Guests see the whole rig and its scenery: fixtures, truss, props, screens and any venue imported from an MVR.
The patch travels with the scene. Addresses, universes and fixture names go with it, because that is what lets the rig light up from live values. If the patch is not something a client should have, do not present the scene.
Guests do not see each other. You see the guest list; guests see neither names nor addresses of other guests. They get no Problems list, no settings and no patch, and nothing they do changes your scene or your camera.
Comments from clients
Only invited guests with Comments can comment. They pin a comment on a light, a truss, a spot on stage or the whole scene. A guest on a forwarded link can never comment.
Every thread is private or public, and private is the default. Private means the writer and your team. Public means also every client shown this scene. Making a thread public shows everything already in it, replies included, so FlexViz asks first.
Client comments arrive in the Comments editor in Present and Review at once, marked (client). Reply answers in the thread, Resolve closes it. Comments covers the rest.
What your client sees of all this is on Join a FlexViz presentation, a page you can send them.