Role-based permissions are configured in Administration > Access Control and control what users can do when they login to your Radar Healthcare system.
If Role permissions are not set correctly then users won’t have access to areas of Radar Healthcare that they expect and won’t be able to perform required actions. Please take care when setting and editing permissions.
You can download a spreadsheet to plan your system role permissions from our article: User Role Permissions Spreadsheet.
Select any of the following links to jump to that part of the guide.
- Assigning Permissions
- Action Plan Permissions
- Analytics custom dashboards permissions
- Analytics Radar Healthcare dashboard permissions
- Audit Permissions
- Document Management Permissions
- Event Reporting Permissions
- Notice Board Permissions
- Report Builder Permissions
- Risk Management Permissions
- Scheduled Tasks Permissions
- System Permissions
- Workforce Compliance Permissions
Assigning Permissions
To assign permissions to roles, select Access Control from the Admin dashboard.
There are two ways to set the permissions, we can either go to each role and select from the permissions list:
Or we can go to the permissions list and select the roles that each permission needs to apply to:
Click the check box with a tick to assign a permission to a role, or alternatively a role to a permission. Ensure you click Save to confirm any changes.
The following list defines what each permission allows within Radar Healthcare.
Action Plan Permissions
- Action Plans - create, assign, prioritise, give a due date and update until complete.
- Please note. When assigned an action the user can view and update it regardless of their permissions.
| Permission Ref | Permission Action |
|---|---|
| Abandon | Can abandon an action plan item. Abandoning an action deletes it from the system and removes all records of this action. |
| Close | Can close action plan items for the location(s). Closing an action allows the user to update and mark the action as complete. Without this permission, a user can update their action, but a user with this permission will need to close it. If a user is being assigned actions, we recommend they have this permission assigned. |
| Create | Can create action plan items for the location(s). This enables a user to be able to create their own actions. For a user to be able to Create an Action, they also need to be able to view Actions. A user may create an action plan item without the view permission via an Event or Audit step. |
| Data Import | Can bulk create actions for a single location. This allows the user to access the Import Action Plan feature in Administration. Using a spreadsheet you are able to upload multiple actions for a single location. |
| Edit | Can edit action plan items for the location(s). This allows a user to edit the details of an action. The 'details' of an action include:
|
| Re-Assign | Can re-assign action plan items for the location(s). The user can assign actions to another user within their Location, Region or Organisation. Please note. If a user re-assigns an action but does not have permission to view all actions, they will no longer be able to see that action. |
| View | Can view the action plan for the location(s). This allows the user to view all actions within their Location, Region or Organisation. For example, a user with a Location role will only be able to view all actions within their location. |
| View Dashboard | Can view action plan dashboard for the location(s). As well as the user’s personal dashboard, there are other dashboards available for each Location, Region and the Organisation as a whole. Whilst any user can choose to view their Location, Region or Organisation Dashboard (which will depend on the role scope), this permission dictates what will appear on the dashboard for that user.For this permission to work, the user must also have the permission to View actions. If the user does not have permission to view all actions, they will be able to see the number of actions outstanding from the dashboard, but will not be able to click through to see what the actions are. |
Analytics custom dashboards permissions
This allows you to grant access for people to view custom analytics dashboards (only applies to customers with custom analytics build licences).
| Permission Ref | Permission Action |
| View custom dashboard "[name of custom dashboard]" | Can view the given custom analytics dashboard |
Analytics Radar Healthcare dashboard permissions
This allows you to choose the dashboards a role in Radar Healthcare has access too. Without any selected, they will not see the Analytics icon on their Dashboard.
Permission Ref | Permission Action |
View Radar Healthcare dashboard "Events" | Can view the Events Analytics Dashboard. Including the number of events raised, the number of open events, the trend of events, when and where are they occurring, and lots more. This dashboard accounts for a user's scope (i.e location). Confidential events and closed locations are not included. |
View Radar Healthcare dashboard "Action_Plans" | Can view the Action Plan Analytics Dashboard. Examples of data include; the number of Action Plans open, overdue, by location, owner and more. This dashboard accounts for a user's scope (i.e location). Data from closed locations are not included. |
| View Radar Healthcare dashboard "Audits" | Can view the Audits Analytics Dashboard. Data includes; average scores, overdue audits, performance over time, audit scores by locations (and more). Audits dashboards do not include ISO audits. This dashboard accounts for a user's scope (i.e location). Confidential audits and data from closed locations are not included. |
| View Radar Healthcare dashboard "Compliance" | Can view the Compliance Analytics Dashboard. Data includes; compliance percentage by type/role/tag, overdue requirements, role matrix, due dates (and more). Org, Region and Location scope are not applied to compliance data, a requirement can exist for a user/role at multiple scopes. Data from closed locations are not included. |
| View Radar Healthcare dashboard "EventRisks" | Can view the Event Risk Dashboard Data includes; average risk score across events, average consequence and likelihood, by type, by location (and more). |
| View Radar Healthcare dashboard "Compliance_Location" | Can view the Compliance Location Analytics Dashboard. Data includes; compliance by location/tag/role, location compliance matrix (and more). Org, Region and Location scope are not applied to compliance data, a requirement can exist for a user/role at multiple scopes. Data from closed locations are not included. |
| View Radar Healthcare dashboard "Document_Downloads" | Can view the Document Downloads Dashboard. This dashboard focuses on the user's downloading of the documents. Data includes; the number of downloads, downloads by function (e.g. notices), list of downloading activity, and more. |
| View Radar Healthcare dashboard "Documents" | Can view the Documents Dashboard. Data includes; % of documents in date, the number of documents with an overdue status, the number of documents split by status, and more. |
| View Radar Healthcare dashboard "Audit_Crystal_Ball" | Can view the Audit Crystal Ball analytics dashboard. This dashboard shows future forecast values based on historic audit data. |
| View Radar Healthcare dashboard "Events_Crystal_Ball" | Can view the Events Crystal Ball analytics dashboard. This dashboard shows future forecast values based on historic event data |
| View Radar Healthcare dashboard "Notices" | Can view the Notices Dashboard. Data includes; the number of notices sent, % of notices confirmed, the number of notices overdue, and more. Org, Region and Location scope permissions are not applied on the notices dashboard. A user with access to this dashboard can view all notices. |
| View Radar Healthcare dashboard "Notices_Matrix" | Can view the Notice Matrix analytics dashboard. This dashboard shows a table of users and notices with a record of if the user has/hasn't confirmed a notice. Org, Region and Location scope permissions are not applied on the notices dashboard - A user with access to this dashboard can view all notices. |
| View Radar Healthcare dashboard "Risk_Register" | Can view the Risk Register analytics dashboard. Examples of data include number and status of open risks, number of risks by score, number of uncontrolled risks Org, Region and Location scope permissions are not applied on the notices dashboard - A user with access to this dashboard can view all risks. |
| View Radar Healthcare dashboard "Risk_Register_Details" | Can view the Risk Register Details analytics dashboard. This dashboard shows all risks along with key details, such as scope, owner, review date, last comment, score, number of controls in place etc. This data can be exported from this page. |
| View Radar Healthcare dashboard "Risk_Register_controls" | Can view the Risk Register controls analytics dashboard. Examples of data include number and status of controls, % by adequacy and assurance, number of overdue controls, controls filterable by owner, risk score and cost of control. |
Audit Permissions
The audit functionality allows you to decide who can create, perform and authorise your organisation’s audits. As with all the permissions in Radar Healthcare, the options selected will only apply for the scope of the user’s role, for example a user with a Location role will only ever be able to access audits within their given Location.
| Permission Ref | Permission Action |
|---|---|
| Abandon | Can abandon audits for the location(s). This allows a user to be able to cancel the completion of an audit that is in progress. This is permanent and will remove all record that the audit was ever scheduled. |
| Add attachment | Can add attachments to the audit summary for location(s). An Auditor can upload files when completing the audit. This permission allows a user to upload files to the audit summary itself. For example, there may be a need to upload a document that does not relate to a specific question. |
| Authorise | Can authorise audits for location(s). Upon completing the questions and assigning actions, an audit requires authorisation. Only users with this permission can be assigned as the Authoriser for an audit. |
| Delete | Can delete audits for the location(s). This is the permission to delete audits that have been scheduled but not started. Once an audit has been started the user would need to abandon the audit to delete it. |
| Delete attachment | Can delete attachments to the audit summary for location(s). An Auditor can delete files when completing the audit. This permission allows the user to delete files in the audit summary itself. |
| Edit Audit at Completion Stage | Can edit audits at the completion stage. After authorising an audit it is marked as complete and is now read-only for users. This permission allows the user to reopen the audit. A completed audit cannot be re-assigned to another user. Only the original Auditor will be able to make changes to the audit. |
| Override Confidential Status | Can set the scheduled audit as confidential or non-confidential before the authorisation stage. Flagging an audit as Confidential restricts who can and cannot view the audit. It is therefore important to ensure that it is given the correct status. |
| Perform | Can perform audits for location(s). In order for a user to be assigned as the auditor, they need to be given the Perform permission. Only users with the perform permission will appear in the auditor drop down list when somebody is scheduling an audit. |
| Reassign Auditor | Can re-assign the auditor for the location(s).This enables a user to reassign an audit that is still Scheduled or In Progress. |
| Reassign Authoriser | Can re-assign the audit authoriser for the location(s). This enables a user to reassign an audit that is still Scheduled or In Progress. If the audit is not started the auditor and authorise can be reassigned at the same time, however if the audit is in progress, the audit must be at the relevant stage of the workflow in order for the authorizer to be reassigned. |
| Schedule | Can schedule and re-schedule audits for the location(s). This allows the user to set when audits need to take place, select the type of audit and assign the auditor and authorizer. It is worth noting that in order for a user to be able to Schedule an audit, they also need to have the permission to View audits. |
| View | Can view the audit lists for the location(s). This allows the user to view all audits within the scope of their role, for example a user with a regional role will be able to see all audits within their Region, but nothing outside of their Region. A user with a location role will be able to see all audits within their Location, but nothing in the wider Organisation. |
| View Confidential Audits | Can schedule and view confidential audits. Flagging an audit as Confidential restricts who can and cannot view the audit. |
| View Dashboard | Can view audit dashboards for the location(s). As well as the user’s personal dashboard, there are other dashboards available for each Location, Region and the Organisation as a whole. Whilst any user can choose to view their Location, Region or Organisation Dashboard (which will depend on the role scope), this permission dictates what will appear on the dashboard for that user. This will allow the user to view the Organisation, Region or Locations audits on their dashboard. For this permission to work effectively, the user must also have the permission to View Audits. |
Document Management Permissions
- Decide whether users are able to view or edit documents within Radar Healthcare.
| Permission Ref | Permission Action |
|---|---|
| Admin User | Can view and manage all documents and folders. This user can upload, edit and manage all documents and folders. This permission overrides any individual document or folder permissions. |
| Basic User | Can view public and granted documents. A basic user can search for and download the latest version of a document in your system. Restrict access to individual roles by utilising individual folder or document permissions. |
For more information on additional document permissions please see Document Permissions Overview.
Event Reporting Permissions
Note: If you are assigned an event you will have certain permissions for that event independent of the permissions set for your role.
| Permission Ref | Permission Action |
|---|---|
| Abandon | Abandon events at the locations(s). This enables a user to cancel and essentially delete an event from Radar Healthcare. Once deleted an event cannot be re-instated, though can be reported on via the report builder. |
| Add Attachment | Add attachments for events at the location(s). As well as being able to capture document uploads as part of the event form questions, there is also the functionality for a document to be attached to the event summary itself. |
| Add Form | Add forms for events at the location(s). As part of an event, you can choose to make optional forms available to users should you wish to do so. This permission allows your users to access these optional forms and add them to their events. |
| Can Create Confidential Events | Has the ability to set an event as confidential for a location(s). There may be incidents where an event needs to be kept confidential, for example, whistleblowing. Flagging an event as Confidential will cause the subsequent steps, such as the event investigation, to be assigned to different roles to those the event would ordinarily be assigned to. This option allows your users to mark an event as confidential at the time of raising it. |
| Can Print Non-Redacted | Users can export the event as a non-redacted PDF. If this permission is not selected, when a user exports an event to PDF, all applicable fields will be shown as REDACTED. These fields include Staff/User lists. When this permission is assigned, the user will be given the option to print Redacted, Reference only (which will display a reference ID for a user rather than their name) or Show all, which will print all names in full. |
| Change workflow task due date | Can change the date by individual workflow steps in an event are due by. In order for a user to be able to change the dates of the workflow, they must also have the View Workflow permission |
| Close | Close events at the location(s). This allows the user to mark events as closed. Please note, that this will also in turn allow a user to Reopen a closed event. |
| Close Event Tasks | Can close event tasks for an event. This allows the user to close any tasks related to an event. |
| Default Confidential Event Assignee | Assigned confidential events at the location(s). When a confidential event is raised, the investigation of the event may need to be assigned to a different user than a non-confidential event. This permission would make this individual the default user to be assigned a confidential event to investigate. Please be aware if more than one user is assigned as the default confidential event assignee, the events will still only be assigned to a single user and this will default to the user uploaded to the system first. |
| Default Event Assignee | Is assigned events for the Location/Region/Organisation if the role as defined in the workflow cannot be found. If there is nobody in the system with the role that the event should be assigned to, this user will be assigned the event in their place. |
| Delete Attachment | Can delete attachments in an event. If a document has been uploaded to support an event this permission allows them to delete it. |
| Edit | Edit events at the location(s). This permission allows the user to edit the details for an event after it has been submitted. In order to edit an event, the user must also have permission to View events or View Own Events. These fields include; Reported by, Date of the event, Time of the event, and Description. |
| Manage Action Plan Items | Can create, edit and close action plan items for the event. |
| Manage Confidential | Manage confidential events at the location(s). |
| Manage Event Tasks | Manage event tasks for events you can access. As part of an event, tasks can be created manually and assigned to a user to complete. This permission allows the user to create, assign and edit these tasks. |
| Manage Workflow | Manage workflow for events at the location(s). This permission allows the user to complete workflow tasks for events that are not assigned to them. In order for a user to be able to manage workflows, they must also have permission to View events and View Workflow. |
| Persons Involved | Can view persons involved in recorded events This permission allows the user to view and search for events using the Persons Involved functionality. Events in the Persons Involved screen will be filtered based on other Event permissions such as Org, Region and Location scope permissions. In order to view events in the Persons Involved screen, the user must also have the View Events permission. |
| Report | Report new events for the location(s). This enables a user to report a new event. |
| Risk Score | Rescore events at the location(s). This gives the user permission to set the risk score for an event or to rescore the event after the initial score has been submitted. |
| View | View recorded events at the location(s). This enable users to view all events within their given Location, Region or Organisation with the exception of confidential events. In order for a user to see the full detail of all steps within an event they will also need to have the permissions to View Workflow and Manage Workflow (depending on how much you detail you would like the user to see). |
| View Analysis Reports | This enables the user to view the pre-set event analysis reports. Please be aware these stats will show all Locations regardless of whether the user has a Location, Region or Organisation role. |
| View Confidential | View confidential events at the location(s). This allows a user to view all confidential events for their Location, Region or Organisation. |
| View Dashboard | View events dashboard widget for the location(s). This gives the user access to view the event dashboard widgets for their Location, Region or Organisation. |
| View events reported by my employees | Can view recorded events that a line manager's employees reported. In order for a manager to view the full details of an employee's reported event they will also need the View Workflow permission. without this permission, they will only see the headline details such as date reported, type of event, description of the event and any initial form completed. |
| View History | View event history at the location(s). Within each event, there is a log of all activity that takes place, including the user, time and date that any changes took place. This permission allows the user to view this history. |
| View Notifications | View the notifications which have been sent as part of the event. When viewing an event there will be a tab called 'Notifications' which will allow you to see how the notification was sent (e.g. email, SMS, etc.), the date/time it was sent, who it was sent to, and the reason (text) provided in the notification. |
| View Own Events | Can view all events where a user is set as the 'Reporter'. This allows users to see events they have raised as the 'Reporter' or that have been raised on their behalf where they are set as the event 'Reporter', after the event is logged. |
| View Workflow | View all workflow for events at the location(s). This allows the user to see the workflow steps associated with an event. In order for users to see workflow steps for events other than their own, the user must also have the permission to View events. |
For more information on additional document permissions please see Event Permissions Overview.
Notice Board Permissions
Radar Healthcare allows you to send notices to your users. The Notice Board Permissions allow you to manage who has access to the notice board admin options.
| Permission Ref | Permission Action |
|---|---|
| Create | Create new notices for the organisation. Please note, a user must also have the permission to View notices in order to be able to Create a notice from the Notice menu item. A user with only the Create permission can create a notice from the Documents section if they are a Documents Admin User. |
| Delete | Delete notices sent to the organisation. A deleted notice will no longer appear for users and if a user has not yet viewed the notice it will not appear for them. In order to delete a notice the user must also have the permission to View notices. |
| View | View all notices sent to the organisation. This enables the user to view the Notices Admin option. This option must be enabled in order to allow a user to create a new notice from the Notices menu item. |
| View matrix report | Can view the notice matrix report. This allows the user to access the notice report and view all notices sent and all users that have been sent notices. They do not need to have the View permission in order to see this. |
Report Builder Permissions
The Report Builder allows the user to build their own reports, pulling through and filtering on the information to show exactly what is important to them. They can then export to CSV for further data manipulation if required.
The reporting access is split into the different Radar Healthcare module types: Audit, Employee Records (Workforce Compliance) and Events.
Please note, in order for the report builder to show any data, the user must have the relevant permissions to view the information requested. For example, if a user has been given access to Event Reports, they also need to have been given access to View Events within the Event Reporting Permissions.
As well as building reports, users are able to save and share reports with other users with the same level of reporting access.
| Permission Ref | Permission Action |
|---|---|
| Audit Report Access | Allows the user to create reports on audits completed in Radar Healthcare. The report results will be filtered based on the users’ other permissions. In order for a user to be able to run reports on all audits within their Location, Region or the Organisation, they must also have the relevant permissions switched on under the Audit permissions section, e.g. “View” to be able to view all non-confidential audits and/or “View Confidential Audits”, in order to include Confidential Audits in the report. Within the reports, users can also click directly into the results table to view a specific audit in more details. The “View” and/or “View Confidential Audits” will allow a user to view the audit details from the Audit report. |
| Employee Record Report Access | Allows the user to create reports on workforce compliance and employee records in Radar Healthcare. If a user needs to be able to run any general user reports from Radar Healthcare, the Employee Record Report Access must be assigned. The report results will be filtered based on the users’ other permissions. With this permission assigned, the user will be able to report on all users within the Organisation, regardless of whether their role is a Location, Region or Organisation role. Within the reports, users can also click directly into the results table to view a specific user’s compliance record in more detail. In order for this to work effectively for all records in the report, the user must also have been given “Admin User” permission from the Compliance and Training permissions. If the user has not be given the “Admin User” permission from the Compliance and Training permissions, then they may still be able to click through to view any user that they directly Line Manage. In this instance, the compliance requirements that the Line Manager sees are determined from within the Permission Rule Sets for the requirements. |
| Event Report Access | Allows the user to create reports on events logged in Radar Healthcare. The report results will be filtered based on the users’ other permissions. In order for a user to be able to run reports on all events within their Location, Region or the Organisation, they must also have the relevant permissions switched on under the Event Reporting permissions section, e.g. “View Own” to be able to report on their own events, “View” to view all non-confidential events and/or “View Confidential”, in order to include Confidential Events in the report. Within the reports, users can also click directly into the results table to view a specific event in more details. Again in order for this to work effectively, the user must also have the appropriate permissions, e.g. View Workflow, View History etc. depending on how in depth the user needs to be able to interrogate the data in the reports. |
| Load Shared Queries | Enables the user to load pre-saved reports from the shared reports folder. The report results will be filtered based on the users’ other permissions. As with the above reports, in order for a shared report to load fully, the user must also have the relevant permissions assigned for Events, Audits or Workforce Compliance. |
| Save Shared Queries | Enables the user to save reports to the shared folder. Saving a report in the shared folder enables all other users with the “Load Shared Queries” permission assigned to load the saved report. Saving a report saves the parameters and filters only and not data itself. In order to save the data from a report, it should be exported as a CSV and saved outside of Radar Healthcare. |
| Scheduled task report access | Grants access to the Scheduled Task report builder. The report results will be filtered based on the users’ other permissions. In order for a user to be able to run reports on all scheduled tasks within their Location, Region or the Organisation, they must also have the "View" permission switched on under the Scheduled tasks permissions section. |
Risk Management Permissions
| Permission Ref | Permission Action |
|---|---|
| Abandon | Abandon risks from the risk register. This enables a user to essentially delete risks from Radar Healthcare. Once deleted a risk cannot be retrieved. |
| Board assurance framework | |
| Create / Edit | Create and edit risks on the organisation risk register. This permission enables the user to add, categorise and score a new risk. This permission also enables the user to edit the details of an existing risk already logged in Radar Healthcare. This includes risks not originally logged by this user. This does not allow the user to rescore an existing risk. In order for a user to be able to Create and Edit the risk register, they must also have the permission to View. |
| Delete updates | Can delete updates relating to comments.In order for a user to be able to delete updates, they also need to have the permission to both View and Review the risk register. |
| Edit updates | Can edit updates relating to comments.In order for a user to be able to edit updates, they also need to have the permission to both View and Review the risk register. |
| Review | Review the risks on the organisation risk register. This permission allows the user to add updates to the risk, including comments, attachments and log actions. This permission also allows the user to set a review date, rescore and close the risk. In order for a user to be able to Review a risk they also need to have the permission to View risks. |
| View | View the organisation Risk Register. This permission includes the ability to view the risk register in the system, as well as being able to export the register as an Excel document or a PDF. The information available to view includes a breakdown of risks per risk category, all risks and the current risk score, related actions and the user to whom the actions are assigned, full history of updates for the risk. This permission is key to enabling all the above Risk Management permissions. |
Scheduled Tasks Permissions
Scheduled tasks enable you to set up automatic actions that will take place at a given point in time. These can be one off tasks or recurring tasks that will automatically re-schedule after the set period.
| Permission Ref | Permission Action |
|---|---|
| Archive | Archive scheduled tasks for the location(s). Archiving a scheduled task means that the schedule itself is archived. If the task was a recurring task previously, the act of archiving the task will mean that the recurrence stops and no further tasks will be assigned to any users. An archived task will no longer appear in the list of Scheduled tasks. Archiving scheduled tasks should be used if a previously regular task no longer needs to take place. In order for a user to be able to archive scheduled tasks, they must also have permission to View. |
| Close Action | Can close actions relating to scheduled tasks. Closing an action for a schedule task means that that instance of the task is now complete. The task will remain in the scheduled task list with a status of “Compliant” until the next task is due at which point the task will re-allocate as per the schedule set. Closing an action should be used to mark that that particular instance of the task is complete. In order for a user to be able to close actions for scheduled tasks, they must also have permission to View. |
| Create | Create new scheduled tasks for the location(s). This permission enables the user to create scheduled tasks for their Location, Region or the Organisation. This includes adding the details for the tasks, assigning the task to a user and setting a notification to send, prioritising the task and setting the recurrence period. In order for a user to be able to create a new scheduled task, they must also have permission to View. |
| Do Form | Can view and complete the required form for a scheduled task. If a task that contains a form is assigned to a user to complete, they must have this permission in order to complete the task. |
| Edit | Edit scheduled tasks for the location(s). This enables the user to edit the details of an existing scheduled task, including those not originally logged by this user. This includes the ability to change the person responsible for completing the tasks, priority level, due date etc. In order for a user to be able to edit a scheduled task, they must also have permission to View. In order for a user to be able to reassign the person responsible for the overall schedule for a task, they must also have the Create permission. |
| Reassign task | Reassign instances of a Scheduled Task. With this permission, the user will be able to reassign an instance of a Scheduled Task. This will not affect the next instance which will continue to assign to the original user who is responsible for that Scheduled Task. |
| View | View and update the scheduled tasks list for the location(s). This permission enables the user to view the details of the scheduled tasks for their Location, Region or the Organisation. This permission also enables the user to add updates in the form of comments or document attachments. This permission is key to enabling all of the above Scheduled Tasks permissions. |
| View Dashboard | View the scheduled tasks dashboard widget for the location(s). This gives the user access to view the Scheduled Tasks dashboard widget for their Location, Region or Organisation. In order for the user to be able to click into the dashboard widget for more information, they must also have permission to View. |
System Permissions
The System Permissions relate to the Administration menu options and cover the wider system management functionality. Any system permissions that are assigned grant access to the whole system and are not limited to the user's location or region.
| Permission Ref | Permission Action |
|---|---|
| Bulk Assignment | Can access bulk assignment tools to configure Radar Healthcare for many users at once. This permission enables the user to assign different items to multiple users. This functionality can be useful, for example, if a user has left the organisation or changed job role and all items assigned to them need to be reassigned to another user. This includes:
The permission will also cover the entire organisation, regardless of the scope of the user’s role. E.g. a Location or Region role user with Bulk Assignment permission assigned, will be able to reassign items relating to all users across the entire system and will not be limited to just the user’s own Location or Region. A user with the Bulk Assignment permission can reassign all of the above items, regardless of any other permissions assigned to them. |
| Can edit forms | Can create and edit forms using the form editor. The form editor is the tool that enables you as an organisation to design and edit the forms used in your events, workforce compliance assignments and scheduled tasks. This permission will allow a user to create and edit any forms in use, and publish the updates to users. |
| Can Grant Event Access | Can assign access to restricted Event Types based on the answer to a question within the event. For example; you may restrict all your recorded incidents, however, if the incident is classified as 'Data Breach' on one of the questions asked you may wish to grant these events to your Data Protection Officer. This way the individual only has access to the specific data related events without seeing any other. See Event Access Group (Event specific permissions) for more information. |
| Can manage tags | User can manage tags. The user can create new by typing in the tags box within the relevant item being created (e.g. action plan or document) or by creating the tag in the Tag Management screen. |
| Can view email client | Can access the email client from the Admin dashboard. The email client allows the user to view all emails that are sent via Radar Healthcare, including the content of the email. |
| Manage Access Control | Can configure the parts of the system each role can access. A user with Manage Access Control permission can set the access across the entire organisation, regardless of the scope of the user’s role. E.g. a Location or Region role user with Manage Access Control assigned, will be able to set the access permissions for all roles across the entire system and will not be limited to just the user’s own Location or Region. A user with the Manage Access Control permission can manage all system permissions, regardless of any other permissions assigned to them. |
| Manage Audits | Can configure audit types and templates. This permissions enables the user to:
A user with Manage Audits permission can manage all audits within the system, regardless of any other permissions assigned to them. |
| Manage Compliance | This permission is a legacy permission and no longer has a function. Radar Healthcare will be removing this permission from the list in due course. |
| Manage Compliance Requirement Assignments | Can create and edit compliance requirement assignments. This enables the user to:
A user with Manage Compliance Requirement Assignments assigned can manage the assignment of requirements across the entire organisation, regardless of the scope of the user’s role. E.g. a Location or Region role user with Manage Compliance Requirement Assignments assigned, will be able to assign or remove requirements for roles and users across the entire system and will not be limited to just the user’s own Location or Region. In order for this permission to activate, the user must also have the Manage Compliance permission assigned. |
| Manage Compliance Requirement Types | Can create and edit compliance requirement types. This permissions enables the user to:
A user with Manage Compliance Requirement Types assigned can manage the compliance requirements across the entire organisation, regardless of the scope of the user’s role. E.g. a Location or Region role user with Manage Compliance Requirement Types assigned, will be able to create and edit requirements and set permissions for those requirements across the entire system and will not be limited to just the user’s own Location or Region. In order for this permission to activate, the user must also have the Manage Compliance permission assigned. |
| Manage Device Registration | Enable and disable mobile devices for the organisation. When a user downloads the Radar Healthcare App and logs in for the first time, they will need to be approved before being able to access the system. This permission enables this user to approve or block users attempting to access the Radar Healthcare App. |
| Manage Events And Risk | Can configure risk matrices and events. This permission enables the user to:
A user with Manage Events And Risk assigned can manage the events and risks across the entire organisation, regardless of the scope of the user’s role. E.g. a Location or Region role user with Manage Events And Risk assigned, will be able to restrict events to roles and set the risks used across the entire system and will not be limited to just the user’s own Location or Region. A user with Manage Events And Risk can manage all of the above, regardless of any other permissions assigned to them. |
| Manage Organisation | Grants access to manage the organisation hierarchy. This permission enables the user to Create, Edit and Delete Regions, Locations and Departments. A user with Manage Organisation assigned can manage the entire organisation, regardless of the scope of the user’s role. E.g. a Location or Region role user with Manage Organisation assigned, will be able to view and manage all areas of the organisation and will not be limited to just the user’s own Location or Region. |
| Manage Training | This permission is a legacy permission and no longer has a function. Radar Healthcare will be removing this permission from the list in due course. |
| Manage Users | Manage users for the organisation. This permission enables the user to:
A user with Manage Users assigned can view and manage all users across the entire organisation, regardless of the scope of the user’s role. E.g. a Location or Region role user with Manage Users assigned, will be able to add and edit users in all areas of the organisation and will not be limited to just the user’s own Location or Region. |
| Set Users Password | Can manually set the password for a user. The set password button reveals a screen to manually set the password for a user, instead of sending an email to the user’s email address. In order for this permission to activate, the user must also have the Manage Users permission assigned. |
| View audit logs | User can view all audit logs. The audit log displays a full history of activity, including the user (email address) that made the change. Activities logged include updates to user records, updates to permissions, updates to roles assigned, updates to modules such as events (newly reported and changes), actions, audits, compliance etc. This permission is not restricted by Org, Region or Location scope. A user with this permission will see all activity. |
Workforce Compliance Permissions
Note: Compliance permissions for individuals and managers need to be set from within the Workforce Compliance section of the system. Please find the article on Creating your Workforce Compliance Permission Rule Sets here.
| Permission Ref | Permission Action |
|---|---|
| Admin User | Can view compliance records for all users within the scope of the role (Organisation / Region / Location) irrespective of Permission Rule Sets |
| Delete User Record | Can permanently delete the entire compliance record for a user |
| View Dashboard | Can view compliance dashboard item |
| View matrix report | Can view matrix report for user(s) at the users's own location, region or organisation |