<aside> ποΈβπ¨οΈ Once you have set permissions levels for users, you can further amend what they can access in Ashby. You can read more about permission levels in our Ashby Permissions guide
</aside>
In Ashby, you can further control what your users have access to by amending visibility settings. Some of these settings can be per user, like limiting or providing additional access to a job or department. Some are set based on their permission group or Global User Role, like seeing previous interview feedback.
If some users require additional access to some roles but limited access to others, weβd recommend setting their Global User Role to Elevated Access. From there, you can specify a department, location or job title and determine the permissions for that user. You can either set a role with certain permissions or restrict access completely.
https://www.loom.com/share/10977587066e4cf186fb1d0ebff7ddde
To set a user to have Elevated Access, navigate to Admin > Organization Setup > Employees. Select the user in question and navigate to the Permissions tab on their profile. User the Role dropdown to set them to have Elevated Access.
Once the user has elevated access, you can then give them access to a team and/or location, or a specific job (or all three). Click the + icon next to either Team and Location Access Roles or Job Access Roles. Then, select the location, team or job from the dropdown. Then select the level of permissions they should have using the Access Role dropdown.
Here is a table showing the permission levels for each access role when assigning them to a department or job. Thereβs more information on these roles available in our Ashby Permissions guide.
Permissions | External Recruiter | Analyst | Hiring Team Member | Hiring Manager | Admin | Admin - Private |
---|---|---|---|---|---|---|
Can see candidate profiles | β | β | β | β | β | β |
Can see email communication | β | β | β | β | β | |
Can see feedback forms | β | β | β | β | ||
Can review applications | β | β | β | |||
Can email/schedule candidates* | β | β | β | |||
Can add/edit candidates | β | β | β | |||
Can access/use the Chrome extension | β | β | β | |||
Can add/edit jobs | β | β | ||||
Can submit feedback on behalf of others | β | β | ||||
Can see/edit hired candidates | β | |||||
Can see private notes/fields | β | |||||
Can create/send/see offers | β | |||||
Can make one-off edits to approval processes (if enabled) ** | β |
** Emailing and scheduling are done using the Google Workspace or Microsoft 365 Integrations. This means users must be a part of your domain to take these actions.*
**For more information on enabling the option to allow one-off amendments to approval processes, check out our guide here.
<aside> ποΈβπ¨οΈ This is not a commonly used feature.
</aside>
To hide a role from many or all other users, you could also opt to make the job confidential. When a job is made confidential, only the creator, users who have been given access to the role and Organization Admins with access to all confidential roles will be able to see it.
You can set a job as confidential or non-confidential, click More when viewing the job. Then click Make Confidential. Only the job creator (or an Organization Admin with access to all confidential jobs) can set a role as confidential or not confidential after the job has been created.
Making a new job confidential
Making an existing job confidential
Removing the confidential status from a job.
You can edit whether and when users with Limited and Elevated Access can see interview feedback, along with whether feedback should be shown in interview briefings and completed feedback notification emails in Admin > Interviews & Scheduling > Feedback Visibility. You can set feedback to always be visible, never be visible or to only show to users after theyβve submitted their own interview feedback.