Using Rivet for consultation and supervision

Rivet video isn’t only for client sessions. Your slug URL works for anyone who shows up — including other practitioners. Supervision, peer consultation groups, case discussion calls, and team meetings all run in the same workspace, with the same tools.

​

When this is useful

A few common patterns where a Rivet video session is the right call:

• Supervision — your supervisor opens your slug URL, taps Join, you start the session. They see your face, you see theirs. If you want to walk through a session note, share your screen and review it together.
• Peer consultation — a colleague taps your URL for a 1:1 case discussion. The same workspace, the same tools.
• Training a new clinician on a tool — share your screen and walk them through how you use a clinical template, the EMDR workspace, or the inbox.
• A second clinician joining a session — case conferences with another provider when the client consents. Note: Rivet’s video is 1:1 — only two browsers connect to a session at once. For a three-way case conference, you’d need a different tool.

​

What’s the same as a client session

Everything. The same pre-join screen, the same workspace, the same toolbar, the same end-call teardown. The slug URL doesn’t know whether the person tapping it is your client or your supervisor — and that’s deliberately a feature. A few practical notes:

• You can share screen with another practitioner just like with a client. Multitrack — they see your face in a corner tile while you show your screen.
• The whiteboard works the same way. Useful for sketching a formulation together with a colleague.
• Sessions are not recorded for consultation either. No recording exists. If you want a record of what was discussed in supervision, take notes.

​

What to skip

The clinical surfaces in the toolbar (EMDR especially) exist for client work. Don’t run BLS at your supervisor — it’s a clinical intervention, not a feature demo. The same applies to the in-session clinical templates: those are for client administration, not for case discussion. If you want to show a colleague how the EMDR or template surfaces look, share your screen with another browser tab where you’re showing those features to yourself. Don’t run them live with a peer as the “client” — you’re polluting your own queue records.

​

A separate URL for non-client use?

You don’t get a second slug for consultation. The one URL covers everything. This is intentional — managing two URLs would mean managing two waiting rooms, and the one-URL design is the entire point of the slug system. In practice this hasn’t caused problems:

• Your supervisor knows they’re not a client and isn’t surprised by the waiting-room page.
• The waiting-room queue shows everyone who’s waiting by first name. Knowing “Sarah” is your supervisor and “Mike” is your 2pm client is trivial.
• If your queue is somehow ambiguous (two people named Mike?), the in-app waiting-room view shows the phone number they entered. That resolves it.

​

Privacy for consultation use

The same privacy properties apply. The session is end-to-end encrypted. The connection setup data is held only briefly while the call is being established. Nothing is recorded. The session duration is logged for audit purposes; the session content is not. If you discuss client information during a consultation, the standard PHIPA / PIPEDA obligations apply to that discussion the same way they would on a phone call or in a hallway conversation. Rivet’s tooling is designed around those obligations but doesn’t substitute for clinical judgment about what’s appropriate to discuss in a consultation. See PHIPA and Rivet for the full custodian framing.

​

Related articles