Give your foreman a login. Not the keys to everything.
Everyone who touches hiring gets their own account and sees exactly what their job needs. Your service manager sees his applicants. Your office admin never sees a wage. Nobody shares a password again.
One of Indeed’s 2025 Platinum ATS Partners.
5,000+ growing businesses hire on AvaHR without a recruiting team.
Seven roles, and one of them already fits.
Nobody should have to design a permission scheme before they can hire. The seven roles that ship with AvaHR already cover how a small team divides the work, and each one’s permissions are fixed, so there is nothing to configure and nothing to get wrong.
Pick the role that matches the job
Seven roles ship with AvaHR, from Owner down to External Recruiter, and each one already has its permissions decided. Most shops only ever use four of them.
Read what it can do, in plain English
Every permission is written the way you would say it out loud. Can they see pay. Can they delete a candidate. Can they see the other three branches. You read the answer instead of designing it.
Assign it and forget it
You put somebody on a role, not on a list of checkboxes. Move them to a different role from one dropdown, and switch their access off the day they leave without deleting anything they wrote.
Seven roles, zero setup
No permission matrix to configure. The built-in roles already fit how small teams actually hire.
The Owner stays in control
One locked Owner account that cannot be removed. Ownership only moves when you choose to transfer it.
Change a role anytime
Move somebody up or down in one click. Their access updates across every job right away.
Seven roles, and the awkward cases are already in them.
The reason a fixed set works for a small team is that the hard parts of access are not preferences. Who sees pay, who can delete somebody, what an outside recruiter can reach, what happens the day a manager leaves. Those answers ship decided.
Owner down to External Recruiter
Each one already has its 19 permissions decided, grouped by the part of hiring they belong to. Most shops only ever use four.
Owner is locked on purpose
Nobody can hand your company to themselves from a dropdown. The Owner role transfers from Company Profile, deliberately, and the row in Team Members shows a padlock where everyone else has a select.
Every other role is a two-click change from that same table, and switching somebody off is one more.
Pay is its own permission
Your lead tech can run interviews all week without ever seeing what anybody earns.
Deactivate, never delete
Switch somebody off the day they leave. Their notes, scores and messages stay on the candidates they touched.
An outside recruiter sees one candidate
External Recruiter is scoped to the people they were invited to, not your pipeline.
Nineteen answers. Nobody has to read a manual.
Every permission is grouped by the part of hiring it belongs to and written in plain language. What a role can do is legible at a glance, which is the only reason anybody ever checks it twice.
Search candidatesSASummit AirAnd a record of who did what.
A role decides what somebody is allowed to do. The activity log says what they actually did, so the candidate who quietly disappeared has a name and a timestamp next to them instead of a shrug.
- Every stage move, message and rejection is attributed
- Role changes are logged too, including who made them
- Blocked attempts show up, so you find the gap before it matters
Search candidatesSASummit AirFour branches, four logins, no forwarded résumés.
“I have four branches and four managers who each think their applicants are the only ones that matter. Now they log in and see their own branch, their own jobs, and not one pay number. I stopped being the person who forwards résumés all day.”
Renee at the Cardinal Plumbing office
What a role opens, and what it keeps shut.
Permissions are not a settings page you visit once. They decide what every other part of AvaHR looks like for the person logging in.
Team collaboration & scorecards
Roles decide who is in the room. Collaboration is what they do once they are there, and it stays attached to the candidate.
Explore →Custom hiring pipeline
Who can move a candidate a stage, and who can only watch it happen, is a switch on the role.
Explore →Enriched candidate profiles
Everybody opens the same profile. What is on it, and what is hidden as a field rather than greyed out, follows the role.
Explore →Automated actions
Rules run on the system's authority, so nothing stalls waiting for the one person who has access to press the button.
Explore →Offer letters & e-signature
Only the roles you name can build or send an offer. Everyone else can see that one went out, and nothing more.
Explore →Insights & analytics
Managers see the numbers for their own branch. You see everybody's, side by side, without asking anyone for a report.
Explore →The practical version.
Most of these come up in the first ten minutes of setup. A specialist will walk your actual org chart with you on a demo.
How many roles can I create?
As many as you need. In practice most companies settle on five: an owner, an admin, a hiring manager, an interviewer, and one named after a title that only exists in their business. Branch Lead, Shop Foreman, Charge Nurse.
Can I hide pay from some people?
Yes. Compensation on the job post, the offer and the candidate's desired rate is a permission of its own. When it is off the field does not render at all, rather than sitting there greyed out and inviting questions.
Can a manager see only their own location?
Yes. A role can be scoped to a location, a department, or a specific list of jobs. A Phoenix manager logging in sees a Phoenix account, not a filtered view of everybody else's.
What happens when somebody leaves?
Deactivate them and their access ends immediately. Their scorecards, notes and messages stay attached to the candidates they worked, because those are part of the hiring record, not their personal file. Nobody inherits their login.
Can I give somebody access to just one job?
Yes. Add them as an interviewer on a single job and that is the whole of what they can see. It is how most companies bring in a lead tech or a shift supervisor for one hire without giving them the run of the account.
If I change a role, does it apply to everyone on it?
Immediately, and to the next person you put on it. That is the point of editing a role rather than a person. The change itself is logged with your name on it.