Eploy's Roles and Permissions allow you to identify all of the key information that each user should have access to, whilst also allowing you to segregate your database to ensure that any private, confidential or sensitive information is stored securely within the system.
Using roles, you can restrict access to internal jobs from certain users, or hide more senior positions from different recruiters or teams. Similarly, you also have greater control over the admin functions in the system, allowing you to grant access to certain records or system areas only to those who require it.
From a user point of view, it also means that you can hide any irrelevant data, making it easier for you to find your jobs, your candidates and your applications to manage.
Roles, Data and Field Access
System Access is made of four components which work together to ensure that all users have access to the right information and features/functionality:
Roles - A role is made up of data access, field access and permission groups. You can create a role for each level of access you require and assign those roles to each of your users. Users can then have multiple roles, which can give them access to different areas of the system at different times.
Data Access - These are allocated to specific roles (one per role) and control exactly which records the user will be able to see whilst using that role. Within data access, you will be able to give access to specific Organisations, Vacancies, Applications and Candidates, whilst restricting visibility of others. This allows you to segregate the database, based on who is logged in.
Field Access - Whilst Data Access looks at the records they can see in the system, Field Access allows you to control which fields can be viewed within those records. For example, Data Access may give visibility of a set of candidates, but Field Access will then restrict them from viewing ED&I or Bank Account information.
Permission Groups - Permission Groups give you the ability to control whether users have Read/Write, Create and Delete permissions for individual areas of the system. For example, an Admin role may have Create and Read/Write permissions to the whole of the system and limited Delete permissions, with a Recruiter role having Create and Read/Write permissions for only the sections of the system they need e.g. Organisations, Contacts, Vacancies, Candidates, etc. A Super User role could then have complete access to the whole of the system including all Delete permissions.