The Lucca Recruitment tool centralizes all applications by job, making it easier to share information with all employees involved in recruitment.
To set up roles, you need to have access to role administration. You can access these settings by clicking on the Lucca settings cogwheel icon, then selecting Roles.
Preconfigured roles
When you install Lucca Recruitment, three secondary roles are preconfigured on your instance.
- Recruitment - Administrator: Administrator is the solution’s most comprehensive role, having all of the permissions listed below
- Recruitment - Recruiter: Recruiters manage the recruitment process (creating and posting job offers), filter and select applicants, track the recruitment pipeline, and update applicants’ statuses. They have full access to all applicant data.
- Recruitment - Manager: A manager can view applicants for a specific job in their team and takes an active part in recruitment by providing their opinion (rating, comment, assessment)
These roles can be edited: you can add or delete one or more permissions to/from these roles at any time.
Roles and their associated permissions
Permission | Details | Manager | Recruiter | Administrator |
Access to the application |
This only requires the application to be selected in the role, without any associated permission This is the minimum role that we recommend you give to all of your company’s employees. |
✅ |
✅ |
✅ |
View job vacancies within a defined scope |
Lets the user view all jobs and all the associated profiles within the defined scope (e.g. all departments) With this permission, it's possible to leave a comment or an assessment on a profile. |
❌ Even if they don't have the permissions required to view jobs, a manager added to a recruitment team will be able to see jobs they've been assigned to. |
✅ | ✅ |
Create, edit, share and archive jobs | Lets the user view archived jobs. | ✅ | ✅ | ✅ |
Create and edit an applicant | Lets the user create an applicant profile for a job and edit the information found in its profile header (contact details, current job, tags, documents) | ✅ | ✅ | ✅ |
Add and move an applicant into a job | Lets the user add a (previously created) applicant to a job or move them from one step to another within a job. | ✅ | ✅ | ✅ |
Move an applicant to the final step of a job |
The final steps for a job are: rejecting the application, or moving it to the final step, which then enables export to Core HR. Only users with this permission can export applicants to Core HR. |
✅ | ✅ | ✅ |
View and manage sensitive comments about an applicant |
Private notes allow for an extra level of subtlety when managing sensitive information. This permission lets the user make a comment private, so that it can only be seen by themselves and administrators with the same permission. |
❌ | ❌ | ✅ |
Create, edit, and delete tags |
Makes it possible to administer tags either from general settings or directly on profiles (create, edit, and delete). The users can then add/delete them on profiles with the permission "Create and edit an applicant". |
❌ | ✅ | ✅ |
View profiles recruited and exported to Core HR |
Makes it possible to keep an applicant’s information confidential after they have been recruited. For example, your new manager will not be able to see the comments and assessments left on their own profile. |
❌ | ✅ | ✅ |
View archived profiles | Makes it possible to display archived profiles. | ❌ | ✅ | ✅ |
Set up the application | Lets the user configure legal information (privacy policy, contact email address for deleting data) | ❌ | ✅ | ✅ |
Set up career pages | Lets the user create and edit career pages, take them offline, and delete them. | ❌ | ✅ | ✅ |
Delete a profile | Lets the user delete all of an applicant’s data (e.g. if they request that you delete their data after an application) | ❌ | ❌ | ✅ |
Exporting data | This enables you to export data from applicant profiles | ❌ | ❌ | ✅ |