Summary and recommendation
Modern Treasury 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.
Modern Treasury supports native SCIM 2.0 provisioning, but it is gated behind the Enterprise plan.
For teams not yet on Enterprise, user management is handled manually through the dashboard at https://app.moderntreasury.com.
Role and permission documentation is largely behind a login wall, which limits pre-sales evaluation.
This pattern repeats across every app that withholds admin tooling from lower-tier plans.
Quick facts
| Admin console path | Settings / Administration > Users and Roles (exact labels vary by tenant) |
| Admin console URL | Official docs |
| SCIM available | Yes |
| SCIM tier required | Enterprise |
| 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: Modern Treasury 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 | Yes | Enterprise |
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: Modern Treasury uses custom pricing starting approximately $499/month; per-seat costs are not publicly listed and are negotiated as part of a contract.
The cost of manual management
Without SCIM, invite, role assignment, and deactivation steps must each be performed individually in the dashboard. Per-seat costs are not publicly listed; pricing is negotiated as part of a custom contract, with reported starting figures around $499/month.
Manual overhead compounds quickly when offboarding requires action across multiple systems simultaneously.
The decision
If your organization is on the Enterprise plan, SCIM is the recommended path for provisioning and deprovisioning - it removes manual steps and reduces offboarding risk across every app connected to your IdP. If you are on a lower tier, budget for manual overhead on every user lifecycle event.
Evaluate whether the volume of user changes justifies upgrading to Enterprise before your next contract renewal.
Bottom line
Modern Treasury is a viable choice for finance teams that need structured payment operations, but its user lifecycle tooling is split: Enterprise customers get full SCIM automation, while everyone else manages users by hand through the dashboard.
The lack of public documentation for permission models and user flows adds friction during evaluation. Factor in the manual overhead cost across every app in your stack when sizing the operational lift.
Automate Modern Treasury 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.
