Live URL
The space’s stable address. Sharing changes never move it.
Show it to your people,
not the whole internet.
New spaces are private: the URL alone doesn’t grant access. Invite people, create share links, or make the space public. You can revoke any of it.
Who can get in
You, from the publish receipt
Every publish returns an access link just for you. It signs your browser in and opens the live URL.
People, invited by email
Invite someone as a Viewer, Commenter or Editor, for the whole space or only some paths. Reviewers and agents don’t add seats. See pricing.
Links, no account required
A link can grant View or Comment access on its own, with no account. Scope it to one or more paths and add an expiry if you want.
Access requests
People who reach a space they can’t see can request access. You approve or deny it without opening the space.
Team or Public
One switch opens the space to your whole team or to everyone. The address and history stay the same.
Comments follow the same access as the page they’re on.
Taking access back
Revoke a Link
Every copy of that link stops working, wherever it was forwarded. Your other Links are untouched.
Remove a person
Only that person loses access.
Log everyone out
Sign out every browser session at once without changing who is invited.
Turn off Public
Only the public grant goes away. Everyone you invited keeps access.
Three URLs, three jobs
Access URL
Opening it signs a browser in and redirects to the live URL. Integrations send the same token, or their own API key, in X-SF-Authorization instead.
Claim URL
Proves ownership of a space published without an account, until you sign in and claim it.
Your agent can do all of it
Every sharing action is one command from the CLI, the API, or MCP.
sf share link create --name "Client review" --path '/report/**' --role commenter --expires 7d
sf share grant --to public --role viewer --path '/assets/**'
sf share people invite ana@studio.example --role editor
