Summary and recommendation
Roadmunk 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.
Roadmunk (now part of Tempo) uses a fixed four-role model: Owner, Administrator, Editor, and Reviewer.
There are no custom roles or granular permission sets beyond these predefined tiers.
Roadmap-level sharing controls which Editors and Reviewers can access specific roadmaps, but account-level role assignment is the primary access boundary.
Every app in a well-governed stack requires a clear seat audit path - Roadmunk's is manual.
The Members list at Account Settings > Members shows all current roles, but last-login timestamps are not surfaced in the UI, so identifying stale Editor seats depends on cross-referencing IdP activity logs.
Quick facts
| Admin console path | Account Settings > Members |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | Professional |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Owner | Full account control: billing, member management, all roadmap access, SSO configuration, and account deletion. | Counts as a paid Editor seat. | Only one Owner per account; ownership can be transferred but not duplicated. | ||
| Administrator | Manage members, configure SSO/SAML, access all roadmaps, adjust account settings. Cannot manage billing. | Cannot access billing or transfer ownership. | Counts as a paid Editor seat. | ||
| Editor | Create, edit, and share roadmaps. Can invite Reviewers to specific roadmaps. | Cannot manage account-level settings, members, or billing. | Paid seat; pricing starts at $19/user/month (Starter, annual) up to $99/user/month (Professional, annual). | Seat count drives billing; each Editor consumes one paid license. | |
| Reviewer | View and comment on roadmaps they have been explicitly shared with. Cannot create or edit roadmaps. | Cannot create roadmaps, edit content, manage members, or access account settings. | Free; Reviewer seats do not consume paid licenses. | Reviewers must be invited per roadmap by an Editor or Admin; they do not have general account access. |
Permission model
- Model type: role-based
- Description: Roadmunk uses a fixed set of four account-level roles (Owner, Administrator, Editor, Reviewer). Roadmap-level sharing controls which Editors and Reviewers can access specific roadmaps. There are no custom roles or granular permission sets beyond these predefined tiers.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Account-level role assignment plus per-roadmap sharing controls. No field-level or object-level permission granularity.
How to add users
- Log in as Owner or Administrator.
- Navigate to Account Settings > Members.
- Click 'Invite Members'.
- Enter the invitee's email address.
- Select the role (Administrator, Editor, or Reviewer).
- Click 'Send Invite'. The invitee receives an email to accept and set up their account.
Required fields: Email address, Role selection
Watch out for:
- Inviting an Editor increases the paid seat count and may affect billing immediately or at next billing cycle depending on plan.
- Reviewer invitations are per-roadmap, not account-wide; they must be sent from within a specific roadmap's share settings.
- Pending invitations occupy a seat until accepted or cancelled, depending on plan configuration.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Professional (SAML SSO required; provisioning available via Okta and OneLogin connectors) |
How to remove or deactivate users
- Can delete users: Yes
- Delete/deactivate behavior: Roadmunk allows Owners and Administrators to remove (delete) members from the account via Account Settings > Members. Removed users lose access immediately. Official docs do not describe a separate 'deactivate' state distinct from removal.
- Log in as Owner or Administrator.
- Navigate to Account Settings > Members.
- Locate the member to remove.
- Click the options menu (three dots or 'Remove') next to the member.
- Confirm removal. The user loses account access immediately.
| Data impact | Behavior |
|---|---|
| Owned records | Roadmaps created by the removed user remain in the account and are accessible to Admins and the Owner. |
| Shared content | Roadmaps previously shared with the removed user remain intact for other collaborators. |
| Integrations | Not documented |
| License freed | Removing an Editor frees the paid seat; the seat count decreases and billing adjusts at the next billing cycle. |
Watch out for:
- Official documentation does not describe a restore or re-invite flow that recovers the removed user's prior settings; re-inviting creates a new member record.
- Roadmaps owned by the removed user are not automatically reassigned; an Admin must manually transfer or manage them.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Editor (paid seat) | Full roadmap creation and editing, account collaboration features. Includes Owner and Administrator roles. | Starter: $19/user/month (annual); Business: $49/editor/month (annual); Professional: $99/user/month (annual); Enterprise: custom pricing. |
| Reviewer (free seat) | View and comment on shared roadmaps only. | Free; unlimited Reviewers on paid plans. |
- Where to check usage: Account Settings > Members - lists all current members and their roles, allowing Admins to audit active Editor seats.
- How to identify unused seats: Review the Members list for Editors who have not logged in recently; Roadmunk does not surface a last-login timestamp in the UI per available documentation, so identification of unused seats may require manual review or IdP activity logs.
- Billing notes: Billing is per Editor seat. Reviewer seats are free. Plan pricing is per-user per-month, billed annually for discounted rates. Seat changes mid-cycle billing behavior is not explicitly documented in publicly available help articles.
The cost of manual management
Editor seats drive billing at $19–$99/user/month depending on plan tier; Reviewer seats are free and unlimited on paid plans. Because Reviewer invitations are scoped per-roadmap rather than account-wide, teams managing large stakeholder groups face repeated per-roadmap invite overhead.
Pending invitations may occupy a paid seat until accepted or cancelled, depending on plan configuration - a detail not explicitly documented in public help articles. Seat changes mid-cycle billing behavior is similarly undocumented, which creates budget uncertainty when onboarding or offboarding Editors at scale.
SSO and provisioning are gated behind the Professional plan ($99/user/month), meaning teams on Starter or Business tiers must handle all user lifecycle events manually through the Members admin console.
What IT admins are saying
Community evidence is not specific enough to quote or summarize yet for this app.
The decision
Roadmunk fits teams that need structured roadmap collaboration with a simple role model and are comfortable with manual user lifecycle management on non-Enterprise plans. Every app decision should weigh the Reviewer-per-roadmap invite model against stakeholder volume - large external review groups will generate disproportionate admin overhead.
If automated provisioning is a requirement, the path runs exclusively through Okta or OneLogin connectors on the Professional/Enterprise tier, with SAML SSO as a hard prerequisite. Teams without an established IdP, or on lower-tier plans, have no programmatic user management path.
Bottom line
Roadmunk's role model is straightforward but inflexible: four fixed roles, no custom permissions, and a Reviewer scope that creates overhead at scale.
Manual user management is the default for most plan tiers, and seat auditing requires IdP log cross-referencing since last-login data is absent from the admin UI.
Automated provisioning is available only via Okta or OneLogin connectors on higher-tier plans, with SAML SSO as a non-negotiable prerequisite - teams should factor both the plan cost and IdP dependency into any lifecycle automation decision.
Automate Roadmunk 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.
