Summary and recommendation
Metronome 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.
Metronome is a usage-based billing platform built for software companies that need to meter, rate, and invoice customers on consumption.
Its admin surface is dashboard-driven, with no native SCIM provisioning documented in official sources.
Every app in your stack that relies on Metronome for billing data must be managed through the dashboard or REST API directly.
Quick facts
| Admin console path | Settings / Administration > Users and Roles (exact labels vary by tenant) |
| SCIM available | No |
| SCIM tier required | Unknown |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Can manage tenant settings, integrations, and user access. | Cannot grant functionality outside the modules licensed for the tenant. | Detailed built-in role names are not fully documented publicly. | ||
| Standard User | Can use the core product features exposed to their role. | May not be able to manage tenant settings or other users. | Exact privileges can vary by tenant configuration. |
Permission model
- Model type: role-based
- Description: Metronome appears to use role-based access for tenant administration and general product use, but the detailed permission matrix is not publicly documented in full.
- Custom roles: Unknown
- Custom roles plan: Not documented
- Granularity: Expect administrative access to be separated from standard user access, with exact scopes configured per tenant.
How to add users
- Log in as an administrator.
- Open settings or administration and navigate to users.
- Choose the add or invite user action.
- Enter the user's work email and assign the appropriate role.
- Save the user and complete any activation or SSO steps required by the tenant.
Required fields: Work email address, Role
Watch out for:
- Public documentation for user administration is limited, so exact labels may vary by tenant.
- If SSO is enabled, upstream IdP assignment may still be required.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Unknown | Not documented |
| Domain whitelisting | Unknown | Automatic domain-based user add |
| IdP provisioning | Unknown | Not documented |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: Public docs do not clearly document whether users are disabled, deleted, or both. Treat lifecycle behavior as tenant-specific unless confirmed in-product.
- Open the users area as an administrator.
- Locate the user to offboard.
- Disable, revoke, or remove the account using the controls available in that tenant.
- Review any integrations or service credentials associated with the departing user.
| Data impact | Behavior |
|---|---|
| Owned records | Tenant data remains in the workspace; public docs do not describe user-owned content semantics in detail. |
| Shared content | Shared dashboards, configurations, and records remain available unless separately removed. |
| Integrations | Review service credentials and integration ownership separately during admin offboarding. |
| License freed | Seat reuse behavior is contract-dependent and not publicly documented in detail. |
Watch out for:
- Offboarding should include token and integration review, not just interactive login removal.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Named user | Administrative or standard access to the tenant. |
- Where to check usage: Settings / Administration > Users and Roles
- How to identify unused seats: Review the tenant user list and any visible login or activity metadata. No public unused-seat report was verified.
- Billing notes: Metronome pricing is usage-based and custom; no publicly documented per-seat licensing model was found in official sources.
The cost of manual management
Metronome's pricing is usage-based and custom across Pro, Business, and Enterprise tiers; no publicly documented per-seat licensing model was found in official sources. A free tier is available, but paid plan pricing requires direct engagement with Metronome.
Because there is no seat-based model to audit, license hygiene work centers on reconciling active billing customers and plan assignments rather than reclaiming unused seats.
The decision
Manual administration is the only documented path for Metronome today - no SCIM, no IdP integration, no automated provisioning. If your team needs to manage a small number of billing customers and can tolerate dashboard-based workflows, the manual approach is viable.
Teams operating at scale, or those requiring every app to reflect real-time customer lifecycle changes, should evaluate the REST API instead.
Bottom line
Metronome fits teams that need flexible, usage-based billing infrastructure and are comfortable managing customer lifecycle through a dashboard or REST API. There is no SCIM or IdP provisioning path, so every app that depends on Metronome customer data requires a deliberate integration strategy.
Given the custom pricing model and absence of per-seat licensing, operational overhead is lower than typical SaaS tools - but the lack of automated provisioning means offboarding and plan changes must be handled explicitly.
Automate Metronome 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.
