Role-Based Access: Who Should See What in a Funding CRM
An owner, a new broker, a syndication investor and an ISO partner all log in to the same system. They should not all see the same thing.
In a lot of funding shops, permissions are an afterthought. Everyone gets the same login type because it was easiest during setup. Then one day a junior broker exports the whole merchant list, or a referral partner notices they can see another partner's deals, or an investor asks why their dashboard shows the owner's Social Security number on a file they participated in.
Role-based access means deciding, by job, what each person can see and do, then assigning people to roles rather than tuning permissions one account at a time. It is how you give a growing team the access they need without giving everyone the keys to everything.
This guide walks through the five roles most funding shops actually have, what each typically needs, and the decisions that cause the most arguments.
Pre-flight summary
- Assign access by role, not person by person, so it stays consistent as the team grows.
- Keep owner access and bulk export with very few people.
- Let brokers work their pipelines fully, but restrict exports by default.
- Scope investors to their own participations and partners to their own submissions.
- Review role assignments regularly, especially on joins, moves and departures.
Leg 01The principle: least access that still gets the job done
The security term is least privilege, but the floor version is simpler: give people what they need to do their job well, and nothing extra. Extra access is not a perk. It is extra risk if their account is compromised, extra temptation if they are planning to leave, and extra liability if a merchant ever asks who could see their information.
Least access does not mean making work harder. A broker who has to ask a manager for every file will find workarounds, and workarounds are where data leaks. The goal is a role design where the normal day flows smoothly and only unusual actions need a higher level.
Leg 02Owners and managers
Owners generally need full visibility: every deal, every broker's activity, financial ledgers, commissions and system settings. They are also the people who approve who else gets what, so owner access should be held by very few people and protected with the strongest second factor available.
Sales managers usually need to see their team's pipelines, listen to call recordings for coaching, reassign deals and run reports. Whether a manager sees company-wide commissions or only their team's numbers is a business decision worth making deliberately. Many shops keep bulk export and user administration with owners only, even if managers otherwise have broad visibility.
FundPilot ships with roles for owners, managers, brokers, investors and partners, and each deployment is tailored during discovery to match how your floor is actually organized, rather than forcing your team into a generic template.
Leg 03Brokers
Brokers need their own pipeline in depth: contact details, documents, underwriting results, lender replies, call history and the dialer. The common debate is whether brokers should see each other's deals. Seeing the whole board can prevent two brokers calling the same merchant; hiding it protects each broker's book and reduces poaching inside the shop.
A workable middle ground is letting brokers see that a merchant is already owned by someone, without opening the file. Restrict exports for brokers by default. A broker rarely has a legitimate need to download a spreadsheet of hundreds of merchants, and if they do, a manager can do it for them.
Extra access is not a perk. It is extra risk the day an account is compromised or a broker gives notice.
Leg 04Investors and syndication participants
If your shop syndicates deals, investors need a window into their participations: amounts, schedules, payments received and payoffs. They do not need merchant identity documents, the broker's call notes or deals they did not participate in.
Consider a hypothetical: an investor takes a 20 percent participation in a deal for a trucking company. Their view should show the participation, the remittance history and their share of collections. It should not show the owner's license photo or the statements used in underwriting. FundPilot keeps participations, schedules and payoffs on one ledger, with an investor role scoped to the investor's own positions.
Leg 05Partners and referral sources
ISOs and referral partners often want to track the deals they sent in. That is reasonable, and giving them a self-serve view cuts down on status calls. The boundary is tight, though: a partner should see only their own submissions, typically at the level of stage and outcome, plus whatever commission information you have agreed to share.
Be careful about what a stage name reveals. A stage called Declined, Existing Positions Too Heavy discloses underwriting detail about a merchant to a third party. Keep partner-visible statuses neutral and save the detail for internal roles.
Leg 06Putting the roles into practice
Designing roles is a one-afternoon exercise for most shops. Keeping them accurate is the ongoing work.
- List every person and outside party who logs in today, and the job they do.
- Group them into roles: owner, manager, broker, investor, partner, and any specialist roles such as a processor.
- For each role, write down what it can view, edit, export and administer.
- Assign people to roles rather than customizing individual accounts.
- Review the list monthly and whenever someone joins, changes jobs or leaves.
- Use the audit trail to spot access being used in ways the role design did not anticipate.
Questions from the floor
Should brokers be able to see each other's deals?
There is no single right answer. Full visibility helps avoid duplicate outreach and supports teamwork; restricted visibility protects individual books and reduces internal poaching. Many shops compromise by showing that a merchant is already assigned without exposing the file itself. Whatever you choose, apply it consistently through the broker role rather than making exceptions for individuals.
What should happen to a broker's deals when they leave?
Deals belong to the company. When a broker leaves, disable their account the same day and reassign their open pipeline to another broker or a manager. Because the deal history, documents, calls and texts are stored on the deal rather than in the broker's personal accounts, the next person can pick up where things stopped without anything walking out the door.
Do investors need any access to merchant information?
Investors usually need enough to understand and track their participation, such as the business name, the deal terms they participated in and the payment history. Identity documents, full bank statements and internal call notes are generally unnecessary. Agree on the investor view in your syndication arrangements and configure the role to match, so the boundary is clear to everyone.
How often should we review who has access?
A monthly check works for most shops, plus an immediate review whenever someone joins, changes jobs or leaves. Look for people in the wrong role, accounts that should have been disabled, and outside parties such as partners or investors who no longer have an active relationship with you. The audit trail helps by showing how access is actually being used, not just how it was configured.
General information only — not legal, tax or financial advice. Rules for telemarketing, texting, recording, disclosures and data retention vary and change; confirm current requirements with qualified counsel.
Connecting flights