Sharing
Send a plan, a play, or a report to someone without giving them an account.
Some things need to leave BenchOS. A play you want a coach at another program to look at. A development plan a parent should read. A weekly report for your athletic director.
A share link is a URL that opens a read-only view of one artifact. No editing, no navigation into the rest of your program, and — depending on what you're sharing — no account required.
Creating one
Open the thing you want to share and press Share. Choose who the link is for, and BenchOS gives you a URL to copy.
Two audiences
Anyone with the link — the page opens for anybody who has the URL, signed in or not.
Members of your program — the page opens only for someone signed in to your program. Anyone else gets a sign-in prompt, not the content.
What you can share
Not everything offers both audiences. Artifacts that name players, show availability, or say who sits are restricted to your program and cannot be made public at all — the choice isn't presented, because the mistake is too easy and too expensive.
| Artifact | Audiences |
|---|---|
| Play | Anyone with the link, or program |
| Drill | Anyone with the link, or program |
| Development plan | Anyone with the link, or program |
| Development card | Anyone with the link, or program |
| Practice plan | Program only |
| Game brief | Program only |
| Rotation | Program only |
| Weekly report | Program only |
| Scouting report | Program only |
Development plans and cards are shareable publicly on purpose: they are the artifact most often sent to a parent or a college coach, and they are about one player who is already the intended audience.
What the recipient sees
A clean, printable page of that one artifact and nothing else — no sidebar, no links into your program, no way to reach anything you didn't share.
Plays and drills carry their diagrams. Everything else renders the document as your staff wrote it.
Managing links
Settings → Shared links lists every link your program has created: what it points at, who it's for, who created it, how many times it's been opened, and when it was last opened.
Revoke kills a link immediately. The URL stops working for everyone who has it, and the entry stays in the list so you can see the link existed and was withdrawn.
There is no expiry date — a link works until someone revokes it. If you shared something with a season in mind, revoking at the end of it is a deliberate act, not something BenchOS does for you.
Things worth knowing
A link is not a permission grant. Sharing a practice plan with your program doesn't let a player open the rest of your practice plans — it opens exactly the one artifact behind that URL.
Creating a link requires being able to see the thing. You can only share what you already have permission to view, so a share link can never widen your own access.
Public links are guessable only in theory. The token is long and random, and unlisted, but treat "anyone with the link" as genuinely public: anywhere the URL travels, the content travels.