What you need first
- A session or submission worth sending. A submission carries every session that player ran, which is usually what a stakeholder wants.
- The recipient’s email, if your plan includes outbound email. They do not need a Userplay account either way.
The playbook
1
Mark it up first
Create highlights at the moments you want the recipient to watch.
Whatever you send is what they see. Recipients cannot make their own highlights.
Creating a highlight
Mark the moments before you send.
Highlights
Generated moments you can lean on instead of marking every one.
2
Open Manage visibility
From the session’s overflow menu, click Manage visibility.
3
Choose Anyone with the link
Pick Anyone with the link, which is public on the internet, over Studio members, which is your team only.The studio confirms with “Anyone with the link can view”.
Sharing a session
The two states, and exactly what a recipient can do.
Roles and permissions
Who already has access without a link, so you know if you need one.
4
Send it
Get the link to your recipient.
- Copy it yourself
- Send from the dialog
Copy link in the header copies the URL.
Email branding
What the recipient’s email looks like when it lands.
Plans and limits
Which plans send outbound email, and which do not.
5
Close it again when they are done
Switch the visibility back to Studio members.
How you know it worked
- The session’s visibility reads as open to anyone with the link.
- Opening the link in a private browser window loads the session without a sign-in.
- The recipient sees the recording and all five panel tabs, but no Create highlight, Export, or Manage visibility controls.
- After you switch it back, the same private window gets a dead end.
Related articles
Sharing a session
The two states, and exactly what a recipient can do.
Creating a highlight
Mark the moments before you send.
Submissions
If one player’s whole run is the better thing to share.
Data retention
A shared link stops working when the session’s window closes.