MCA Software User Roles & Permissions Explained
MCA software user roles control everything a person can see and do, scoped to whether they belong to a funder, an ISO, or a merchant organization. A role is set by the organization’s administrator and ranges from full administrative control down to a read-only view of the advances list. MCA Track ships eleven standard roles and lets Funder Admins build custom roles from 145 granular permissions for users who fall between the presets.
Key takeaways
- Your role is set by your organization’s administrator and controls everything you can see and do, including what appears in the top navigation.
- MCA Track has eleven standard roles spread across three organization types: funder, ISO, and merchant.
- Funder Admins can build custom roles from 145 granular permissions, each a specific action on a specific record type.
- Most feature areas follow the same List, View, Create, Edit, Delete, and Full-access pattern, with extra specialized permissions where noted.
- Per-user toggles such as Hide DBA, Hide Commission, SSN access, and Whitelist IPs fine-tune what an individual sees on top of their role.
What are user roles in MCA Track?
A user role is the controlling permission set for an account. Your role is set by your organization’s administrator and controls everything you can see and do; even the items in the top navigation depend on it. Roles are scoped to one of three organization types — funder (the capital provider), ISO (the sales and origination partner), or merchant (the funded business).
User management belongs to Funder Admins. MCA Track supports both the standard role system and fully custom permission sets, plus a set of per-user switches that fine-tune what individuals see. For ISO staff, logins are created from the ISO’s own detail page so each person is tied to that partner and sees only their merchants and information.
What are the eleven standard user roles?
The eleven standard roles cover every level of access, from a Funder Admin with full control of the business down to an Overview Only ISO role limited to a read-only view of the cash advances list. The table below summarizes each role and its organization type.
| Role | Org | What they can do |
|---|---|---|
| Funder Admin | Funder | Full control of the funder’s business — merchants, advances, payments, ACH, syndicators, users, preferences, roles, and reporting (cannot create or edit routing numbers). |
| Funder Underwriter | Funder | Full merchant, advance, payment, and document management plus the entire lead-underwriting flow. No syndicators, disbursements, preferences, or custom roles. |
| Funder User | Funder | Day-to-day work on merchants and advances (create and edit, not delete). Read-only on payments, fees, syndicators, and ISOs. No ACH or admin functions. |
| Funder Sales Rep | Funder | Read-only merchants and advances; full lead lifecycle; notes and expenses. No financial records or user management. |
| Funder Relationship Manager | Funder | Read-only oversight across ISOs, merchants, advances, users, and documents. Edits expenses only. |
| ISO Admin | ISO | Oversees the ISO’s portfolio and pipeline: view merchants and advances, edit merchants, full lead lifecycle, ISO preferences, and the ISO/syndicator dashboard. |
| ISO User | ISO | View merchants and advances, manage leads, upload and download documents. No financial records or user management. |
| ISO Sales Rep | ISO | Focused on leads — full lead lifecycle, events, and documents. No write access to merchants or advances. |
| ISO Underwriting Only | ISO | Lead processing only (including quick-entry). No merchant, advance, payment, or document access outside leads. |
| Overview Only | ISO | Most restricted ISO role — a read-only window into the cash advances list. |
| Merchant User | Merchant | The business owner: views their own merchant record, advances, and statements; uploads and downloads documents. |
How do custom roles and the permission catalog work?
A custom role bundles a precise subset of the 145 permissions and is assigned as the controlling set for a user’s account. Each permission is a specific action on a specific record type — for example, view cash advances, cancel an ACH transaction, or export a commission report. Only Funder Admins can create, edit, or assign them.
The permission catalog draws on those 145 permissions across every feature area. Most areas follow the same pattern — List (see the index), View (open one record), Create, Edit, Delete, and Full access — with extra specialized permissions where noted, such as Renew on Cash Advances or Download on Documents. Templates can be cloned and tweaked per user, so one team member can have a slightly different set than everyone else on the same template. Custom roles are ideal for users who fall between Funder Admin and Funder User, such as a billing specialist who should see payments and fees but not leads or ACH configuration.
What per-user settings fine-tune access?
Beyond the role itself, a set of per-user switches refine what an individual sees. These are set on the user’s edit screen and layer on top of whatever role applies. Hide DBA masks merchant trade names — useful for syndicators who should see only MIDs or reference codes — while Hide Commission hides commission figures in reports and on merchant pages.
Other switches govern sensitive access: SSN access controls viewing Social Security numbers, bank account info access reveals full bank and routing numbers, and Whitelist IPs restricts a user’s login to specific IP addresses. Multi-factor authentication options live in security settings. Underwriting access is required for funder underwriters to reach the leads and underwriting module.
Roles determine who can run each step of the funding flow, from creating and funding a merchant to managing cash advances, renewals, and reups. To map roles to your team, book a walkthrough → or return to the complete MCA servicing software guide.
Frequently asked questions
MCA Track has eleven standard roles spread across three organization types: funder, ISO, and merchant. They range from Funder Admin with full control down to the Overview Only ISO role with a read-only view of the cash advances list.
Only Funder Admins can create, edit, or assign custom roles. A custom role bundles a precise subset of the 145 granular permissions and is assigned as the controlling set for a user’s account.
Custom roles draw on 145 granular permissions across every feature area. Most areas follow the same List, View, Create, Edit, Delete, and Full-access pattern, with extra specialized permissions where noted.
Hide DBA masks merchant trade names, which is useful for syndicators who should see only MIDs or reference codes. It is one of several per-user switches set on the user’s edit screen, on top of whatever role applies.