Summary and recommendation
Charles River IMS 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.
Charles River IMS is an enterprise-only investment management platform sold exclusively via custom contract, and it stands apart from every app that publishes a public admin console or help center.
No self-serve tier exists, and all administration documentation is delivered through implementation engagements and a gated client portal.
Step-by-step user-management workflows, role structures, and deactivation behavior cannot be independently verified from public sources.
Quick facts
| Admin console path | Settings / Administration > Users and Roles (exact labels vary by tenant) |
| 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 |
|---|---|---|---|---|---|
| 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: Charles River IMS 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: Charles River IMS is an enterprise-only platform sold via custom contract. Pricing and seat licensing details are not publicly disclosed.
The cost of manual management
Without a documented admin console path or public user-management guide, IT and ops teams cannot standardize onboarding or offboarding the way they can with tools that publish their workflows. Every manual action-adding a user, adjusting permissions, or deactivating a leaver-requires coordination with your Charles River implementation contact or internal documentation produced during your deployment.
This creates an operational dependency that scales poorly as headcount changes.
The decision
Unlike every app that offers self-service admin tooling, Charles River IMS requires user lifecycle management to be a vendor-assisted process. Confirm during contract or renewal negotiations what admin tooling, documentation, and support SLAs are included.
Identify who internally owns the relationship with Charles River Development (a State Street company) and ensure that person is looped into any identity or access management initiatives.
Bottom line
Charles River IMS is a closed, enterprise-only platform where user administration details are not publicly documented and are only accessible through authenticated client portals or direct vendor engagement.
Teams should treat every app in their stack that lacks public admin documentation-Charles River IMS included-as requiring a dedicated internal runbook built during implementation, since no public source can substitute for it.
Operational continuity depends on maintaining a strong vendor relationship and capturing institutional knowledge at deployment time.
Automate Charles River IMS 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.
