More precise access control
Admins can align permissions with team structure instead of using a one-size-fits-all setup for every user.
ATZ CRM added team-based roles and permissions, in-app timesheet notifications, and company merge controls for cleaner team access, staffing follow-up, and account data hygiene.
Create teams and assign users to the right group
Define roles and permissions for each team
Receive in-app alerts for candidate-submitted working hours
Get notified when clients approve or reject timesheets
Merge company records while keeping associated details intact
Quick answer
This operations update helps admins and recruiters manage control points inside ATZ CRM. Admins can create teams, assign users, and define roles and permissions by team. Recruiters receive in-app notifications when candidate hours are submitted or client timesheets are approved or rejected. Teams can also merge company records without losing associated details.
What changed
Teams in Roles & Permissions gives admins a stronger structure for controlling access. Users can be grouped into teams, and each team can receive the role and permission setup that matches how the agency operates.
In-app timesheet notifications keep recruiters informed when candidates submit working hours through the Candidate Portal and when clients approve or reject timesheets through the Client Portal or email approval link.
Merge Companies helps teams clean duplicate company records without losing associated information. This is useful when the same client, vendor, or company has been created more than once across business-development and delivery workflows.
Together, these updates improve operational control: who can access what, which timesheet events need attention, and how account records stay clean as the database grows.
Why it matters
Recruiters are often measured on speed, quality, and follow-through. This update is designed to reduce manual work, protect useful context, and help teams keep hiring activity moving with fewer handoffs.
Admins can align permissions with team structure instead of using a one-size-fits-all setup for every user.
Recruiters can respond sooner when working hours are submitted or when a client approval decision arrives.
Duplicate companies can be merged while preserving the details recruiters and account managers need later.
Team access, approval alerts, and company cleanup are handled closer to the records where recruiters already work.
Before and after
Before
Permission setup was harder to align with real recruiting teams, branches, or delivery groups.
After
Admins can create teams, assign users, and define team-specific roles and permissions.
Before
Recruiters had to check timesheet status more often to know whether candidate hours or client decisions had arrived.
After
In-app notifications surface candidate submissions and client approval outcomes as they happen.
Before
Duplicate company records could split context across more than one account profile.
After
Teams can merge company records into a cleaner account view while retaining associated details.
How recruiters use it
The exact setup depends on your workspace and permissions, but the core workflow is built to keep recruiters closer to the record, the next action, and the right team context.
Decide which users belong together by branch, desk, role, client group, or operating model.
Set access rules that match each team’s responsibilities and review sensitive permissions before rollout.
Use in-app notifications to act when candidate hours are submitted or a client approves or rejects a timesheet.
Review duplicate company records carefully, choose the correct destination record, and merge when the account context is clear.
After permission updates or company merges, check that users still see the records they need and that account history remains usable.
Feature-specific details
Some releases affect more than one recruiting workflow. These notes explain the practical details recruiters, admins, or managers may want to review before rolling the update out to the team.
Admin checklist
These controls affect access, billing follow-up, and account history, so a quick admin review helps avoid messy downstream work.
Best fit
Admins managing recruiters across teams or branches
Agencies with different permission needs by desk or client group
Temporary staffing teams using timesheets
Recruiters who need quick alerts for approval outcomes
Operations users cleaning duplicate company records
Helpful next steps
Quick answers
They let admins create user groups, assign users to those groups, and define permissions that match each team’s responsibilities.
Recruiters receive in-app notifications when candidates submit working hours and when clients approve or reject timesheets.
Yes. Client approval can happen through an email link or through the Client Portal, depending on the workflow used.
It helps combine duplicate company records while retaining associated details that the team needs for account and recruiting history.
Admins or operations leaders should manage permission rules because access decisions affect data visibility, collaboration, and process control.
No. A person should review duplicate records first to confirm they represent the same company and that the merge target is correct.
See it in context
Book a walkthrough with the ATZ CRM team to see how this update supports your jobs, candidates, and shortlist process.