Baremetrics User Management Guide

• Model type: role-based
• Description: Baremetrics uses a simple two-level model: an Owner with full administrative control and Team Members with read/analytics access. No granular permission sets or custom roles are documented.
• Custom roles: No
• Custom roles plan: Not documented
• Granularity: Coarse. No documented ability to restrict access to specific metrics, data sources, or features on a per-user basis.

1. Log in as Owner.
2. Navigate to Settings → Team Members (https://app.baremetrics.com/settings/team).
3. Enter the invitee's email address in the invite field.
4. Click 'Send Invite'.
5. Invitee receives an email and must accept to gain access.

Required fields: Email address of invitee

Watch out for:

• Only the account Owner can invite team members.
• Invitee must accept the email invitation before access is granted.
• No documented limit on number of team members, but no explicit confirmation of unlimited seats either.

• Can delete users: Yes
• Delete/deactivate behavior: Team members can be removed from the account via the Team Members settings page. Removal revokes access immediately. No documented deactivation/suspension state separate from full removal.

1. Log in as Owner.
2. Navigate to Settings → Team Members (https://app.baremetrics.com/settings/team).
3. Locate the team member to remove.
4. Click the remove or revoke action next to their name.
5. Confirm removal.

Watch out for:

• No documented deactivation or suspension option; removal is the only access revocation mechanism.
• Removed users lose access immediately upon removal.
• No documented audit log of team member actions available to verify post-removal.

• Where to check usage: Settings → Team Members (https://app.baremetrics.com/settings/team) to view current team members.
• How to identify unused seats: No documented last-login or activity tracking per team member to identify inactive users.
• Billing notes: Baremetrics pricing is MRR-based, not per-seat. Plans scale with the volume of MRR processed. Adding or removing team members has no direct billing impact.

Because Baremetrics has no documented role-based access control or granular permission model, IT and ops teams have no reliable way to audit who has access or what they can see. Onboarding a new team member means navigating an undocumented admin flow with no confirmation of what access is actually granted.

Offboarding carries real risk: there is no deactivation step documented, no automated revocation, and no seat-based billing model to flag orphaned accounts. Every departure requires a manual check to confirm access has been removed. Without a structured permission model, verifying the blast radius of any given account is guesswork.

Community feedback consistently flags the absence of enterprise identity features as a gap. Reviewers note that SSO, SCIM, and IdP integration are not available, which limits Baremetrics' fit for teams with compliance or access governance requirements.

Users also raise concerns about pricing relative to feature depth, particularly for teams that need more than analytics dashboards. The lack of publicly documented RBAC or granular permissions makes it difficult to evaluate team management capabilities before committing to a plan.

Common complaints:

• No enterprise identity features such as SSO, SCIM provisioning, or IdP integration documented.
• Considered expensive by some users relative to feature set, particularly as MRR scales.
• Lack of publicly documented granular role-based access control makes it difficult to assess team management capabilities before purchasing.
• No SCIM or automated provisioning support confirmed, requiring fully manual user management.
• No documented per-user activity tracking or audit logs, making it difficult to identify inactive team members.
• Only a single Owner role with full admin rights; no documented way to delegate specific administrative functions to other users.

Baremetrics is a strong fit for small SaaS teams that need fast, clear subscription analytics and are already using Stripe or a supported billing source. It is not a fit for organizations that require centralized identity management, automated provisioning, or audit-ready access controls.

If your IT or security team needs to enforce least-privilege access or demonstrate offboarding completeness, Baremetrics' current feature set will require manual compensating controls. Factor that operational overhead into any evaluation.

Bottom line

Baremetrics delivers genuine value as a subscription analytics layer for MRR-driven businesses, but it carries meaningful IT overhead for any team that needs structured access management.

There is no SCIM, no SSO, no documented permission model, and no seat-based billing to help track who holds access.

Every app in your stack that lacks automated provisioning adds to the manual burden on IT and ops - and Baremetrics, in its current form, is one of those apps.

Teams with light compliance requirements and a small, stable user base will absorb that cost easily; teams with stricter governance needs should plan for the gap explicitly.