Site Visits - New Permission
Currently, any user can mark a site visit record as Completed. Although a snapshot of the last completed site visit details are displayed to the users above the site visits table, we made sure there is an extra layer of permission involved in performing this action. Hence, starting from today we have added a new user role permission to perform this action.
This new user role permission is within the Roles and Permissions area from the admin dashboard, allowing you to decide which user role should have the ability to dismiss the alert messages against the placement record. By default this permission will be available only for the admin role.
This permission is labelled as:
- Can Complete Site Visits
Merge Company - Remove Gateway Details
During the previous release, we have removed the restriction from deleting the Gateway related companies and added a new warning message that will just notify the users while deleting the company records on JR.Direct that are associated to the Gateway employer account.
Starting from this week, when a child company record is being merged into a parent record, and if the child company has a Gateway employer account associated, the system will now merge the child company into the parent company and delete the child company record from both JR.Direct and Gateway systems.
Alerts - Dismiss Alert Messages
A few months ago, we have introduced a feature that will allow the users to dismiss the pop-up alert messages against the placement records. Starting from today, we are extending this feature across all other entities where the alerts messages are available.
Dismissing the alert messages feature would become handy where there might be records migrated from an older database or where the information is stored elsewhere for some records. This can be a problem where users are trying to process information and the alert messages that are showing are not true anymore. With this new feature, you will now have the ability to bypass the alert messages by marking them as dismissed. An activity log record is also captured to show the action that was performed.
This is restricted by a user role permission that has been included within the Roles and Permissions area from the admin dashboard, allowing you to decide which user role should have the ability to dismiss the alert messages against the placement record. By default this permission will be available only for the admin role.
This permission is labelled as:
- Can Dismiss Alerts
Candidates - Delete Option
We have been receiving a lot of requests through Zendesk and emails from customers requesting us to delete the candidate records that might have been created mistakenly or sometimes the candidates would not like to have their details with the providers anymore.
Since the candidate deletion process is a little critical as there are multiple associated records linked to a single candidate record. We as a team always use to make sure the requests comes through us first so that we can delete the candidate records for you manually from the backend of the system.
But starting from today on JR.Direct, we have added a new feature on the candidates page that will allow the users to delete a candidate record and its associated records from the system directly without being dependant on our support team anymore. You will find a Delete this candidate link at the bottom of the candidate page. Once clicked, a confirmation pop-up window will display all the associated records that will be removed along with the selected candidate record. This will also remove the jobseeker account from Gateway.
This is restricted by a user role permission that has been included within the Roles and Permissions area from the admin dashboard, allowing you to decide which user role should have the ability to dismiss the alert messages against the placement record. By default this permission will be available only for the admin role.
This permission is labelled as:
- Can Delete a Candidate
