Orgs & Members

An Org is the company-level container in River. It owns billing, member management, integrations at the org level, and one or more shared Dataspaces.

If you're using River alone, you can ignore Orgs — your personal Dataspace doesn't need one. The moment you bring a teammate in, you're working in an Org.

Anatomy of an Org#

Org
├── Members (people with access)
├── Dataspaces (one personal-team + any team Dataspaces)
├── Integrations (connected at the org level, available to all)
├── Billing & seats
└── Admin settings (auth, ACL defaults, audit logs)

Members#

A member belongs to one or more Orgs. Each Org membership has a role that determines what they can do:

You invite members from Settings → Members → Invite. By default they get Member; promote as needed.

Dataspaces inside an Org#

Every Org has at least one team Dataspace. You can create more — for instance, a "Sensitive" Dataspace for HR or M&A material that not all members should see.

Creating Dataspaces inside an Org is how you partition trust. It's stronger than per-Group permissions because the AI in one Dataspace literally cannot see the other.

Switching between Orgs#

The Org switcher is in the top-left chrome alongside the Dataspace switcher. Switching changes the entire context: members, integrations, billing, and the set of Dataspaces you can see.

You can be a member of multiple Orgs at once (your day job, your side project, a client engagement). Each is fully isolated.

Personal vs. Org#

Your personal Dataspace lives outside any Org. Things you put there are yours, even if you leave every Org you've ever joined.

A common pattern: keep personal email, personal notes, and life admin in your personal Dataspace; keep work in the team Dataspace.

Tips#

• Create one Org per company you work with. Don't co-mingle.
• Use multiple Dataspaces inside an Org when you have data that not all members should see.
• The Owner role is highest privilege — limit it to one or two trusted people. Promote others to Admin instead.