Sharing

You can share anything in River — an entity, a Group, a Space, even a custom App — with anyone, on the inside or outside of your Org.

Three sharing patterns#

1. Share within your Dataspace#

Most of the time, you don't need to "share" inside a team Dataspace — entities are already visible to all members by default. You're just collaborating in the same world model.

If you want to scope something more narrowly than the Dataspace, set an ACL on that entity or Group. See Permissions.

2. Invite a guest#

To share with someone outside your Org, click Share on the entity, Space, or Group. Add their email. They receive a guest invite.

Guests:

• Sign in with the email you invited
• See only what you shared — nothing else
• Can edit (or read-only, your choice)
• Don't count against your seat limit (typically)

This is how most external collaboration works: clients, contractors, advisors, design partners.

3. Public link#

For low-trust read-only sharing, generate a public link. Anyone with the URL can view, but cannot edit.

Use a public link for:

• Open-source documentation
• Read-only project pages
• Public-facing dashboards or status pages
• Marketing content built in River and embedded elsewhere

You can revoke a public link at any time — and password-protect it if needed.

What you can share#

Sharing flows that work well#

• Client deliverables — share a Group with the client as a guest. They see drafts, comments, and revisions, in real time.
• Investor updates — share a Page with a public link, password-protect it.
• External research — share a Group of clipped articles + your synthesis with an advisor.
• Custom App for a customer — publish to a subdomain, share the URL.

Tips#

• Default to inviting guests instead of public links. Auth is cheap; auth-less leaks aren't.
• For a single one-off Doc, public links are fine. For ongoing collaboration, use guests.
• Audit your shared things periodically — Settings → Sharing → Active shares lists everything currently exposed.