Summary and recommendation
Roam Research user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
Roam Research is a note-taking and knowledge management tool built around a bidirectional-linking graph model.
It is designed primarily for individual researchers and knowledge workers, not for enterprise or team IT administration.
There is no organization account model, no admin console, and no centralized seat management
every app in a typical SaaS provisioning workflow that relies on SSO, SCIM, or org-level billing will find Roam Research outside that pattern entirely.
Quick facts
| Admin console path | Roam Research has no centralized organization admin console. Access is managed at the individual graph level through the graph share or multiplayer settings. |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | N/A |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Graph Owner | Full control over a Roam graph: read, write, share, and manage access to that graph. | No documented ability to manage other users' accounts or billing centrally across multiple users. | Pro or Believer | $15/user/month or $180/user/year (Pro); $500/user/5 years (Believer) | Each user holds their own subscription independently. There is no documented team or organization seat model that allows a single admin to provision or deprovision other users' accounts. |
Permission model
- Model type: custom-roles
- Description: Roam Research uses per-graph sharing with three documented access levels: read-only, edit (comment), and full edit. These are set per graph by the graph owner when sharing. There is no organization-wide role-based access control or admin console.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Per-graph sharing with read-only, comment, or edit access levels. No page-level or block-level permission controls are publicly documented.
How to add users
- Graph owner navigates to their Roam graph.
- Opens the '...' (ellipsis) menu or graph settings.
- Selects 'Share' or 'Multiplayer' settings.
- Enters the email address of the person to invite.
- Selects the access level (read-only or edit).
- Sends the invitation.
Required fields: Invitee email address
Watch out for:
- Multiplayer/shared graph access requires the invitee to have their own active Roam Research subscription.
- There is no centralized admin console to add users across multiple graphs at once.
- No bulk invite or CSV import is documented.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | No | Not documented |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: Official documentation does not explicitly describe a deactivate or delete workflow for removing a collaborator from a shared graph. No documented distinction between deactivation and deletion of graph access.
- Official steps for revoking graph access are not explicitly documented in publicly available Roam Research help materials.
| Data impact | Behavior |
|---|---|
| Owned records | Not documented officially. |
| Shared content | Not documented officially. |
| Integrations | Not documented officially. |
| License freed | Each user manages their own subscription independently; removing a collaborator from a graph does not affect their personal subscription or billing. |
Watch out for:
- Because each user holds an independent subscription, an admin cannot cancel another user's license.
- No official documentation describes what happens to content contributed by a removed collaborator.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Pro | Full access to Roam Research features, multiplayer graph sharing, sync across devices. | $15/user/month or $180/user/year |
| Believer | All Pro features plus early access to new features. | $500/user for 5 years (~$8.33/user/month) |
- Where to check usage: No centralized admin dashboard for license usage is publicly documented. Each user manages their own subscription via their individual account settings.
- How to identify unused seats: No documented mechanism for an admin to identify unused seats across multiple users, as there is no team/org billing model.
- Billing notes: Roam Research does not publicly document a team or enterprise billing tier. Each user purchases and manages their own subscription independently. No volume discounts or centralized invoicing are documented.
The cost of manual management
Each user purchases and manages their own subscription independently - Pro at $15/user/month or $180/user/year, or Believer at $500 per user for five years. Because there is no team billing tier, IT or operations teams cannot issue, track, or revoke licenses centrally.
Identifying unused access across a group of users has no documented mechanism, and no volume discounts or centralized invoicing are publicly available.
What IT admins are saying
Community evidence is not specific enough to quote or summarize yet for this app.
The decision
Roam Research fits individual contributors and small research groups who self-manage their own accounts. It does not fit IT-managed environments that require centralized provisioning, deprovisioning, SSO enforcement, or audit-ready access controls.
If your organization needs to onboard or offboard every app through a directory like Okta, Entra ID, or Google Workspace, Roam Research cannot participate in that workflow today. Teams evaluating it for broader rollout should treat the per-user subscription model and absence of an admin console as structural constraints, not roadmap gaps.
Bottom line
Roam Research is a capable personal knowledge tool that sits entirely outside standard enterprise identity and access management patterns.
There is no admin console, no org-level billing, no SSO, and no SCIM - provisioning and deprovisioning must be handled manually at the individual subscription level, with no documented revocation workflow for shared graph access.
Organizations that need lifecycle management across every app in their stack should treat Roam Research as unmanaged software until an enterprise tier with identity integrations is publicly documented.
Automate Roam Research workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
