Customer-facing work
Someone following up with customers may need to find and update relevant records. Consider whether they also need to export the entire customer list.
A practical guide for small teams · 01
When someone leaves, who can still open your CRM?
A shared customer history is useful only when the right people can reach it. Make account setup, role changes, and departures part of the same manageable routine.
Start with the handoff. Map who approves access and who removes it when a person leaves.
Explore the access workflow
01 / Decision points
Note in the marginJob titles can be misleading. Start with the tasks a person actually needs to do.
Decide the boundaries before inviting people in.
In a small business, one person may handle sales, service, and operations. That makes a simple access plan more useful than a long list of permissions nobody owns.
01
What does the person need to do?
Separate viewing customer records from editing them, exporting data, and changing account settings. Ask whether each action is necessary for the work.
02
Who can approve a change?
Choose an owner for access requests and a backup. Agree on how a manager signals a new starter, a changed responsibility, or a departure.
03
What needs to remain with the team?
Before removing an account, identify open opportunities, assigned customer conversations, and other work that needs a new owner.
02 / The working plan
Four moments to put on the checklist.
Use this table to discuss your process and compare CRM software. The right controls depend on the product, so verify each capability rather than assuming it is available.
| Moment | Team routine | What to evaluate in a CRM |
|---|---|---|
| New starter | Confirm the approver, work responsibilities, and start date. Give the person an individual account rather than sharing a login. | Can an administrator invite individual users and assign a role during setup? Can the team distinguish active and pending accounts? |
| Role change | Review what the person needs now, not just what they needed before. Remove permissions that no longer match their tasks. | Can permissions be changed without rebuilding the account? Check how access to records, exports, and settings is controlled. |
| Regular review | Have the access owner compare the user list with current staff and contractors. Investigate unfamiliar or no-longer-needed accounts. | Can you see a useful list of users and their roles? Ask what account activity or administrative history is available for review. |
| Departure | Arrange a handoff of owned work, then remove access according to your departure process. Record who completed the steps and when. | Can access be disabled or removed promptly? Find out what happens to assigned records and whether ownership can be transferred. |
On a narrow screen, scroll sideways to read the full table.
03 / Responsibilities, not titles
Illustrative example / 01
Illustrative example / 02
Illustrative example / 03
Build roles around the work in front of you.
These are starting points for discussion, not a prescribed set of CRM roles. Check the permissions a product actually offers and adjust them to your team.
Team oversight
A manager may need a broader view of work across the team. Discuss whether that responsibility also requires permission to change account settings.
Account administration
An access owner may need to invite people and adjust roles. Identify a backup and keep this responsibility separate from everyday customer work where practical.
04 / Takeaway
A short review beats a forgotten list.
Choose a review cadence your team can maintain, and include access changes in your usual people handoffs. Keep the decisions somewhere the responsible people can find them.
Return to the workflow table
Before you close the guide
- Name an access owner and a backup.
- List the tasks each role needs to perform.
- Check how the CRM handles individual accounts and permissions.
- Agree on a departure handoff and a way to confirm access was removed.
- Set a date to review the user list again.