Julie leads an IT transformation for an industrial SMB: business sponsors, systems integrator, freelance UX and her own firm. Everyone accepts an online meeting—not an eleventh login. Guest accounts expire, freelancers reject desktop agents—and the project drifts into email where a short sync would decide.
The account wall on open projects
When the client mandates their tool, Julie adapts. When she facilitates, forcing accounts blocks half the room: short-mission vendor, one-off expert, sponsor on a shared PC.
The client wants clear traceability; the freelancer wants zero install. Without a middle ground, workshops degrade into email screenshots—slow and ambiguous for wireframes or schedules.
- Refusal to create an account “for one hour”
- IT policies blocking heavy clients
- Vendors juggling multiple tenants
- Decisions delayed for lack of a simple shared space
Invite by link, join in the browser
Meeting by Leagora is link-first: Julie creates a Project room (12), copies the permanent link or a session link for a specific slot, and drops it in the calendar invite. Participants open a recent browser, allow the mic if needed, and enter—no desktop client.
For a twenty-person scoping session she briefly uses a Workshop room (25); for the weekly committee, Project stays the right size.
- Browser access with no install
- Optional dedicated session links per meeting
- Project room (12) for client, vendors and team
- Free trial: one hour for two participants
Waiting room and client-side trust
The client sponsor fears uninvited ears on numbers. Julie uses the waiting room: she sees who knocks, admits the expected vendor, rejects a link forwarded by mistake. It replaces brittle guest-account workflows.
On paid plans, a custom domain reinforces recognition—the link matches Julie's contractual frame, not an anonymous generic service.
Table: who joins how
Julie sends the same flow to everyone; only role and duration change.
The client's internal team can keep their chat; Julie does not try to replace it—she offers a synchronous place for decisions, then actions go back to writing.
| Profile | Constraint | Meeting by Leagora flow |
|---|---|---|
| Client sponsor | No new tool | Link + browser, waiting room |
| Freelance UX | 3-day mission | Session link, no account |
| Integrator | Locked laptop | Browser, no desktop agent |
| Julie (consultant) | Runs committee | Permanent Project room + live recap |
Scenario: design arbitration between client and vendor
Julie books forty-five minutes in the Project room. Client and vendor use the same link; Julie admits the vendor from the waiting room. The freelancer shares screen; the sponsor reads labels without squinting—on the Project plan, Full HD helps with dense mockups.
If the client still hesitates, Julie offers the free two-participant trial for a no-commitment test run.
Frequently asked questions
The guest path is link-based: join in the browser with no install. The host manages the room; external stakeholders enter for the slot duration.
It lets the host control who enters before opening discussion—useful when a client forwarding chain leaks the link.
Project room (12) covers most committees. Beyond that, Workshop (25) hosts a large workshop with a dedicated link.
Meeting by Leagora is hosted in France with a GDPR-aligned approach—often cited with European clients sensitive to contractual framing.