Pomio CRM lets you decide how far each role reaches: a person’s own records, their team or the whole organisation. Many small businesses never make that choice consciously. Either everyone sees and changes everything, because that was the quickest setup, or every salesperson works in a private corner of the CRM and nobody knows what a colleague is doing with the same customer. Both extremes cost money, in different ways.
Why hiding deals from colleagues backfires
When salespeople cannot see each other’s deals, the CRM stops being a shared memory. Two people quote the same prospect without knowing it, and the customer notices before the team does. When someone is ill or on holiday, a customer who calls with a question reaches a colleague who cannot see the offer, the agreed price or the last conversation. New colleagues cannot learn from deals that were won or lost, and the weekly review becomes a set of individual updates that nobody can check. Secrecy also makes it harder to reassign open deals when an owner leaves, because nobody knows what is in them.
Why letting everyone edit everything backfires too
The opposite setup has its own problems. If every salesperson can change any deal, stages and amounts move without the owner knowing, and a well-meant correction can quietly change a colleague’s forecast or commission. Arguments about who owns a customer get settled by whoever edits the record last. And the wider the access, the more customer data each account can reach, which matters when a laptop is lost or a login is misused. Seeing a deal and changing it are two different rights, and they deserve two different answers.
A practical default: see the team, edit your own
For most sales teams of five to fifty people, a simple rule works. Salespeople can view the deals, companies and contacts of their own team, and edit only the records they own. Each deal keeps one clear owner, so it is always obvious who changes the stage, the amount and the close date. If a colleague spots something, such as a newer contact or an outdated amount, they add a note or tell the owner instead of changing the deal themselves. That keeps the pipeline transparent without turning it into a shared document that anyone can rewrite.
When to narrow what people see
Some situations justify less visibility. Separate locations or business units that sell to different markets rarely need each other’s pipeline, so team scope should follow the real team rather than the whole company. Freelance or external sales agents usually see only the deals they work on. Very sensitive deals, such as a takeover discussion or a confidential tender, can sit with a small group. Write these exceptions down and keep them few; if half the deals are exceptions, the rule is wrong.
Managers, finance and directors
A sales manager needs the whole team’s deals to coach and forecast, so team scope is the natural fit. Directors and finance often only need to read figures, not change them, which is what a viewer role is for. None of them need administrator rights to see the numbers: administration is about users and settings, not seniority, as explained in how many administrators a small business CRM should have. The difference between what someone may do and how far that reaches is set out in how own, team and tenant scope work.
Keep earnings personal
Seeing a colleague’s deals is not the same as seeing their pay. Commission statements, targets with personal bonuses and similar figures should be visible to the person themselves, their manager and a small group, as described for commission calculated in the CRM. Agree this in the same conversation as deal visibility, so nobody is surprised by what they can or cannot see.
Write the rule down and check it
Put the visibility rule on one page: who sees which team, who edits what, which exceptions exist and who decides about new ones. It only works when every user has their own login, because a shared account makes scope meaningless. Check the setup during the quarterly access review, especially after people change teams, and rely on an audit trail of who changed what when a deal changed without the owner knowing why.
How Pomio CRM helps
Pomio CRM has four roles: sales rep, sales manager, viewer and organisation admin. Each permission carries a scope, own, team or organisation, which is enforced on the server, so two people with the same kind of right can still see different sets of records. Sales reps see their own figures by default and managers see their team. Every deal has an owner, and the audit log shows who did what and when, without passwords or multi-factor secrets. An overview of the capabilities is on the features page.
A practical checklist
Let salespeople view their own team’s deals; let only the owner edit a deal; give every deal one owner; ask colleagues to add a note instead of changing someone else’s deal; give sales managers team scope; use a read-only role for directors and finance; keep administrator rights for users and settings; define teams by how people really sell; keep exceptions few and written down; keep earnings visible only to the person, their manager and a small group; give every user their own login; review scopes every quarter and after team changes.
Further reading
Does seeing each other’s deals make salespeople compete harder?
Sometimes, and that is usually healthy when the rules for ownership are clear. Problems start when visibility comes without clear ownership, because then seeing a deal invites taking it over.
Should salespeople see deals from other teams?
Only when the teams sell to the same customers. Otherwise team scope is enough, and organisation-wide access stays with managers and a small group.
What if a colleague has better information about a deal?
They add a note or contact the owner. The owner updates the deal, so stage, amount and close date always reflect one person’s judgement.
Can visibility be changed later?
Yes. Start with team view and own edit, and adjust when the team grows or splits. Record the change and check it in the next access review.