Summary and recommendation
Murex 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.
Murex MX.3 is an enterprise capital-markets platform deployed on-premises or in private cloud environments.
User-management documentation is not publicly accessible - it is gated behind client support portals and delivered through professional services engagements.
Because of this, no verified step-by-step provisioning or deprovisioning workflow can be published here.
Every app in your stack that touches Murex will face the same documentation wall until your team engages directly with Murex support.
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: Murex 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: Public seat-level licensing details are not fully documented.
The cost of manual management
Without automated provisioning, access changes - onboarding, role updates, offboarding - depend on internal LDAP/Active Directory integration or direct administration within the MX.3 GUI. This creates audit gaps and delayed deprovisioning that compound at scale in capital-markets environments where access control is a compliance requirement.
Manual coordination with internal administrators or Murex-certified implementation partners is the only confirmed path forward.
The decision
Every app decision around provisioning and access governance for MX.3 must be scoped directly with Murex or a certified partner under an active support contract. Pricing is enterprise-only and custom; no tier-based feature differentiation for access management has been publicly confirmed.
Plan for professional services involvement before committing to any provisioning architecture.
Bottom line
Murex MX.3 is a closed, enterprise-only capital-markets platform with no publicly documented user-management workflows, admin console paths, or role structures. Every app integration touching MX.3 must be scoped directly with Murex or a certified implementation partner under an active support contract.
Treat any third-party documentation as unverified until confirmed against your specific deployment.
Automate Murex 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.
