Draw the qualification path
List who creates the lead, records qualification, accepts the opportunity, and reviews its progress. For each action, distinguish viewing from creating, editing, exporting, and deleting information.
Operations field guide / SaaS sales
Evaluate CRM permissions around the work your sales organization actually does, from qualification to handoff. Give distributed teams a shared way to discuss ownership without opening every record to everyone.
Use a sample deal to make access decisions tangible. The board is a discussion aid, not a product interface.
02 / The practical challenge
A sales development representative qualifies an account, an account executive takes the opportunity forward, and a regional manager steps in for coverage. Each person may need different information and different editing rights.
When everyone can edit everything, ownership and qualification details can become harder to trace. Sensitive notes may reach people who do not need them for their work.
When a handoff leaves the next owner unable to see the relevant context, the team may repeat discovery or route requests through an administrator at an awkward moment.
03 / Workflow guide
Use least privilege as a starting principle: give each role the access needed for its responsibilities, then examine the exceptions. Ask vendors or administrators how their CRM handles each step.
List who creates the lead, records qualification, accepts the opportunity, and reviews its progress. For each action, distinguish viewing from creating, editing, exporting, and deleting information.
Ask whether access can be scoped by role, record ownership, team, or territory. Test what happens when an opportunity moves between representatives or regions. Does the previous owner still need access, and for what purpose?
Consider a manager covering for an absent representative or a specialist joining a deal. Explore how temporary or shared access is granted, who approves it, and how it is removed when the work ends.
Ask what administrators can see about assigned permissions and changes to access. Check whether the available records are useful for reviewing ownership changes and investigating unexpected edits.
04 / Discussion tool
| Example role | Work to consider | Question to test |
|---|---|---|
| Sales development | Qualify a lead and document the discovery context. | Can the representative update qualification without editing unrelated opportunities? |
| Account executive | Accept ownership and advance the deal. | Does the new owner see the context needed after the handoff? |
| Sales manager | Review pipeline and support a deal. | What visibility is needed across the team, and when is editing appropriate? |
| CRM administrator | Maintain access and investigate issues. | Who approves changes, and how can assignments be reviewed? |
Illustrative roles and questions. Your team’s responsibilities and access decisions may differ.
05 / Keep the map current
A permission model is a working agreement, not a one-time configuration. Agree on an owner and a review cadence that fits your organization, then revisit access when teams or territories change.
Who has moved teams, left the organization, or taken on a temporary assignment? Does their access still match their work?
Which transferred deals still need shared visibility? Who decides when the former owner’s access should change?
Are elevated or temporary permissions still needed? Record the reason, approver, and a date to revisit them.
Can the CRM expose enough information to answer these questions? Ask to walk through the review with a representative scenario.
06 / Questions for the room
Not necessarily. First distinguish accountability for the opportunity from the ability to contribute. Ask how the CRM represents ownership and whether collaborators can receive appropriate access without changing the owner.
Start with the teams and territories they actually oversee. Then test cross-region coverage and escalation scenarios. Ask how visibility can be scoped and how changes are approved when coverage shifts.
Bring a sample handoff and ask to see how roles, record access, ownership changes, and permission reviews are handled. Include an exception, such as temporary coverage, rather than testing only the standard path.