Session access & control¶
A Drovio session is a live stream of a host screen, or part of a screen, that guests can interact with. This page describes who can get in, and what they are allowed to do once they are in.
Joining a session¶
Guests are invited either from the contact list inside the Drovio app, or by sharing the meeting link through any channel (email, chat, calendar invite, Slack, Teams...).
The link is not a key
Holding the meeting link is not enough to enter a session. The link brings the guest to the door: the host validates each guest individually before they get in, and can refuse them. Nobody can join your screen without you letting them in, unless you explicitely configured remote desktop access.
Guests joining from a web browser don't need a Drovio account, and they don't have to install anything: they open the link, provide a display name and wait for the host to let them in. Guests using the Drovio app join the same way, and they must be authorized by the host as well.
What guests can see¶
When starting a session, the host chooses what to share:
- a full screen, or
- a portion of their screen, or
- a single application window
Guests only ever receive what the host is actually sharing. On both Drovio editions, this stream travels peer to peer between the participants and is never visible to Drovio Server (see Architecture & data flow).
Remote control¶
What sets Drovio apart from plain screen sharing is that guests can act on the shared machine: they send mouse and keyboard input, which the host's machine replays locally.
- Remote control is available to guests by default once they are in the session
- The host can revoke it at any time during the session
macOS asks for permissions
On macOS, the operating system requires an explicit authorization before Drovio can replay inputs. Drovio must be granted the Screen & System Audio Recording and Accessibility permissions in System Settings → Privacy & Security, otherwise remote control stays inactive whatever the in-session setting. See Drovio app and why we need permissions on macOS and how to grant them.
What this means for you¶
- The meeting link as an invitation, not a credential. It gets a guest to the waiting step, not into the session.
- Share a single application window rather than the full screen when the session only concerns one tool.
- Remember that guests can type on the shared machine, and revoke remote control when you only need them to watch.