// Recruitment Technology, Recruitment Strategies
Shared CRM Logins Cost You Attribution Before They Cost You Security
Published: 23 October 2026,
7 min to read
The bottom line
Per-seat CRM pricing rarely makes room for VAs, resourcers, finance staff or hiring managers. So agencies hand out a shared login. Attribution, the audit trail, performance data and clean offboarding all go with it. Build deliberate tiered access for non-billing users before a fee split argument forces you to.
Per-seat pricing and the CRM seat your agency never bought
Most agencies discover their permissions model in the middle of an argument about a fee split.
A placement lands. Two people claim the sourcing. The CRM says one account did all of it. The resourcer has been logging in as the consultant since March.
That is where best practices for managing CRM user permissions stop being an IT topic.
The cause is pricing, not carelessness. Most recruitment CRMs charge per seat, and price every seat as though it belongs to a biller.
Your agency does not run on billers alone. It runs on resourcers, VAs, payroll, compliance and the occasional director who only wants to look.
Why does per-seat pricing push agencies into shared user accounts?
Because a full user license is priced for a consultant, and most people who need login access are not consultants.
Count the roles around a modern desk that need CRM data without billing against it. An offshore resourcer building longlists. A VA booking interviews. Payroll chasing contractor timesheets. A compliance officer checking right-to-work documents. A hiring manager at a key account who wants to see a shortlist.
At full seat price, finance says no to most of them. So somebody creates one account, names it resourcing, and the password lands in a WhatsApp group.
Every agency has one login that three people know and nobody remembers creating.
The workaround is rational in the moment and expensive over a year. Shared user accounts spread quietly, because nothing breaks on the day you create one. By the time anyone counts them, nobody can say which login belongs to whom.
It is also one of the quieter reasons CRM adoption stalls. Half the team is working inside an identity that is not theirs.
What does your CRM lose when two people share one login?
Four things, and attribution goes first. Every note, call, task and status change lands on the wrong name, or on no name anyone trusts.
That matters commercially because of how agencies pay people. 34.25% of agencies measure recruiter performance primarily through placements and revenue. Another 31.51% blend outcomes with activity metrics.
Activity metrics are worthless when the activity belongs to a shared account. You cannot run a leaderboard on a login.
Second, the audit trail stops being evidence. A candidate asks who called them. A client disputes who sent the CV first. The user record returns an account name and nothing else.
Third, data protection gets harder to argue. A subject access request expects you to show who touched a candidate record and when. A shared seat cannot answer that.
Fourth, offboarding stops working. You cannot disable a leaver without locking out the three colleagues who use the same credentials.
The damage compounds in a stack that already leaks context. It is the same root cause behind data silos in recruitment.
How should access levels work for non-billing users?
Start from least privilege and build upward, rather than cloning a consultant profile and deleting things.
The principle is simple. Grant access to the records a job function needs, and nothing past it.
A practical ladder for a recruitment desk looks like this:
Most CRM systems can express this through permission sets rather than a bespoke profile per person. Define the set once, attach it to a role, and new joiners inherit the right data on day one. Leavers lose it the same way, in one action rather than five.
The commercial argument writes itself. Observers and restricted users should not cost what a biller costs, and increasingly they do not.
Platforms built for enterprise recruitment treat tiered access as standard rather than an upsell.
- Observer. Read-only across pipelines and dashboards, with no edit rights and no contact details. Useful for directors and non-executive board members.
- Resourcer or VA. Full read and write on candidate records and longlists, with field level security hiding fee, margin, salary and commission data.
- Finance and payroll. Placements, invoices, rate cards and contractor timesheets only, with no view of candidate notes or client pipelines.
- Client-side hiring manager. One shortlist, their own live roles, and nothing else in your database.
- Consultant. The full seat, with write access across candidates, clients, live roles and opportunities.
Which permissions habits actually hold up on a live desk?
The ones that run without anybody remembering to run them. Policies written into a handbook decay, and access updates that fire automatically do not.
Start with the security floor, because it is cheap. Individual accounts make multi factor authentication possible, and shared ones make it meaningless. Credential abuse appears in 39% of all breaches once the full attack chain is counted.
Then fix the exit. 33% of former employees say nobody clearly owned shutting off their access. Another 79% kept at least one working account after their last day.
In recruitment those numbers have teeth. A departing consultant with live credentials is a competitor holding your dormant database.
Review permission changes on a schedule rather than on suspicion. Temporary access granted for one search has a way of becoming permanent. A quarterly pass over who can reach sensitive data takes an hour and settles most compliance questions.
None of it holds unless the capture layer is automatic. Attribution survives a busy quarter when every call, email, meeting and note logs itself against the person who made it.
That is the design behind Atlas, an AI-powered recruitment CRM that uses agentic AI to strip admin out of record-keeping. Its AI agents enrich records and update the system on their own, so accuracy never depends on manual logging.
Consultant-level dashboards then break placements down by person and period, which only works when the underlying attribution is clean.
Frequently asked questions (FAQs) on CRM user permissions for recruitment agencies
Almost always. Most CRM contracts license the software per named user, so a shared account breaches the terms first. Data protection rules then add a second problem, because you must show which individual accessed a candidate record.
Fewer full seats than you think, and more total users. Count your billers for full licenses, then map everyone else to a restricted tier. Most agencies find resourcers, finance, compliance and read-only observers outnumber consultants. None of them needs write access to client pipelines.
Candidate records, longlists, shortlists and their own task queue. They should not see fee percentages, margin, client contract terms or the commercial notes on an account. Field level security handles this without a separate database or a parallel spreadsheet.
That depends on the vendor, and it is worth asking directly during procurement. Some platforms price observer and client-side access well below a consultant seat, while others charge the same. The pricing model shapes your permissions model, so raise it before you sign.
Accept that the historical record stays imperfect, then draw a line. Issue individual accounts and reset the shared password on the same day. Treat that switchover date as the start of trustworthy data. For the period before it, rely on email and call records tied to individual mailboxes.
Export the user list and compare it against your current payroll. Anyone on the first list but missing from the second should be disabled the same day. Then look for generic account names such as admin, resourcing, recruitment or info. Those are the shared credentials.
The access decision that makes your billing data worth reading
Shared credentials are a pricing workaround that quietly invalidates the data your agency makes decisions with.
Fix the access tiers and attribution fixes itself, along with the audit trail and the offboarding.
The deeper fix is to stop depending on recruiters to log their own work. Agentic AI can capture calls, emails, meetings and notes in the background and file them against the right person automatically. Built on that principle, Atlas keeps the record accurate whether a consultant, a resourcer, a VA or a coordinator did the work.
Worth a look if your team’s access model has outgrown the seats you pay for.
