Candidate Suggestions
Candidate suggestions and internal marketplace applications follow the same pattern: a person is put forward for a resource request, someone reviews it, and the people involved are informed by email. The ‘Candidate suggestions’ administration page defines, per role, who reviews and who is informed in both of these processes.
To open the page, select the Administration menu item, expand the ‘Resource management’ section and select ‘Candidate suggestions’. Every user that has the permission ‘Manage Users, Teams & Permissions’ can adjust this configuration (see: Permissions).
The page has two tabs:
- Candidate suggestions applies when a candidate is suggested for a resource request, in the request’s ‘Candidates’ tab.
- Marketplace applications applies when someone applies for a resource request through the internal marketplace.
Both tabs are configured in the same way, so everything described below applies to either of them.
The configuration table
Each tab shows one table with five role columns: Requestor, Resource Manager, Project Manager, Team Lead and Candidate. On the ‘Marketplace applications’ tab the last column is called Applicant, because there the person put forward is the one who applied.
The rows are:
Receives the review task: the roles set to ‘Yes’ here get a review task on their ‘My tasks’ page whenever a candidate is suggested or an application is submitted.
Email when a candidate is suggested manually / when an application is submitted: informs the selected roles that a new suggestion or application exists.
Email when a candidate is suggested automatically (candidate suggestions only): informs the selected roles that the automatic resource request feature has suggested candidates. It is separate from the manual email above so it can be switched off on its own, and it starts with the manual email’s settings so nothing changes for recipients until an administrator adjusts it. All five role columns apply, the same as for the manual suggestion email.
Email when the suggestion is approved / when the application is accepted: informs the selected roles about a positive decision.
Email when the suggestion is rejected / when the application is rejected: informs the selected roles about a negative decision. For marketplace applications the rejection reason, if one was given, is included in the email.
The Candidate column cannot be set on the ‘Receives the review task’ row, because a candidate does not review their own suggestion or application. It can be set on the email rows, so the candidate or applicant can be told about the outcome.
If no role is set to receive the review task, a warning is shown on the tab and no task is created for that process. The emails are unaffected by this and are still sent according to their own rows.
Review tasks
A review task makes the suggestion or application visible on the recipient’s ‘My tasks’ page and links to the resource request it belongs to.
Selecting a review task opens the suggestion or application directly for review. For a marketplace application this shows the applicant’s motivation, availability and self-assessment, with Accept and Reject available to reviewers who may edit the resource request. Once the application is decided, or withdrawn by the applicant, the task disappears from the ‘My tasks’ page.
Receiving the review task does not by itself grant the right to decide. Approving or rejecting a candidate suggestion remains reserved for the requestor of the resource request, for anyone who may edit that request, and for their substitutes (see: Delegations). Accepting or rejecting a marketplace application requires edit permission on the resource request. A recipient who is not allowed to view the request’s applications is told so when opening the task. Configure the review task for roles that also hold the corresponding permission, otherwise the task is shown to someone who cannot act on it.
Until a process is configured, decídalo keeps its previous behaviour: for candidate suggestions the requestor of the resource request receives the task, and for marketplace applications no review task is created at all. As soon as at least one role is set on a tab, only the roles selected there receive the task.
Emails
The email rows correspond to email notifications that are also listed on the Notifications page, where each of the two processes appears as one grouped row.
The switch above the table (‘Candidate suggestion emails active’ or ‘Marketplace application emails active’) turns every email of that process on or off at once. It is the same setting as the ‘Active’ flag of the grouped row on the Email notifications page, so changing it in one place also changes it in the other. The switch is shown as active as long as at least one of the process’s emails is active; switching it off deactivates all of them.
The emails about an approved, accepted or rejected decision are switched off by default, so they only start going out once an administrator activates them and selects the roles that should receive them.
To stop a single email while the others keep going out, set all of its role columns to ‘No’: an email with no recipient role is never sent. The switch above the table is the on/off control for the process as a whole.
Two rules always apply, regardless of the configuration:
- The person who performed the action is never informed about their own decision.
- Recipients can still opt out of these emails individually in their account settings, as described under Notifications.
For more information on the following topics, please refer to