Security in the CV workflow of vacancies and projects
FollowConcepts and Functionality
It is possible to set security permissions in CV workflows (both for CVs within job postings and within projects), which will affect the CVs that can be viewed, saved, and deleted in the relevant sections.
- These restrictions, when applied, work in addition to:
- the permissions already set in the statuses of job posting and project workflows
- the permissions configured in the Permissions section of a posting or project’s Properties
Configuration
- Go to Settings > Application > Workflow > select a CV-related Workflow
- Click on a Status or an Outcome
- Scroll to the Permissions section at the bottom: you can select the default option All users are allowed access or Only specified users are allowed access
-
To set up security for specific users:
- Click on Add user > select the users > Add and set the allowed permissions (Allow) or restrictions (Deny)
- Click on the corresponding icon: if the icon is bold, it is selected; otherwise, it is deselected
Note: In this context, denials related to any user or group the user belongs to will always override permissions
Exceptions
- Regardless of the security settings in the CV workflow, new résumés can always be created or added to a job posting or project
- Changing a status directly from the Actions > Change status menu is always possible even if the user does not have access to the selected status or outcome. To prevent this, the Restrictive flag must be enabled in the Workflow
- Viewing permission for a status or outcome has no exceptions except for data not directly linked to CVs in job postings or projects, such as email messages, tasks, or interviews
- Denying the permission to modify an outcome prevents saving information in the CV’s detail form but does not prevent assigning that outcome. To prevent the assignment, the viewing permission must also be denied
Comments
0 comments
Please sign in to leave a comment.