Amélie works solo with clients in France and Switzerland. Each online meeting is a touchpoint: discovery, workshop, readout. She does not want to reconfigure the tool every time; she wants a collaborative space that carries her professionalism and the client’s—from the link received to session end.
Technical name vs display name
Early on Amélie reused the default generated name. A CMO opened the link while screen-sharing to the executive committee—“My Project room” helped nobody frame the topic.
She now separates internal id and display name: “Q3 readout — Brand X” visible as soon as people enter the virtual office, including on shared session links.
Permissions matched to the scenario
In discovery Amélie stays operator and lets the client present to walk through their org. In readout she flips: she presents, the client committee listens as observers where needed.
She picks room size by format: Team (5) for pairs, Project (12) for a marketing committee, Workshop (25) for a multi-squad workshop—always in the browser with no install.
- Discovery: client presenter, consultant operator
- Executive readout: consultant presenter, client observers
- Workshop: named co-presenters, others active observers
Session links and QR
Amélie generates one session link per appointment and shows the QR in the client meeting room when some join on site. Same guest path: no mandatory account, JWT access for the planned duration.
She puts the room display name in the email subject so link, QR and meeting title tell the same story.
Connecting brand, access and format
On long missions Amélie combines subdomain or custom domain (DomainSettings) with waiting room on sensitive committees—brand and permission topics complement each other without duplicating setup.
| Need | Setting | Room format |
|---|---|---|
| Weekly client sync | Display name + session link | Team (5) |
| Project committee | Permissions + QR | Project (12) |
| Co-creation workshop | Multiple presenters | Workshop (25) |
| URL-sensitive client | DomainSettings | By headcount |
Scenario: readout and next mission
Amélie closes a digital transformation mission in a Project (12) room named for the readout. Client-side observers do not trigger screen share by mistake; the QR welcomes a late joiner from the open plan.
Before opening the space to the client she runs the free one-hour two-participant trial with a peer consultant: display name, permissions, link and QR—a fifteen-minute checklist.
Frequently asked questions
No: the id supports management; display name is what hosts and guests see on entry.
Amélie picks the room suited to headcount; each size stays a distinct virtual office in her space.
Yes for the intended guest path on the session; Amélie checks date and time before sending.
When the client requires it or to align with an existing subdomain; otherwise display name and session link are often enough.