This article will outline each role within the Navitas DFS system and what actions they can and cannot complete displayed through a table format and user personas. User Permissions The below table will outline the permissions that each DFS User Role has within the system and detail which actions can be completed by each role.

Creating User Accounts

The system is built so that each role can only add new users with a role that is lower in the hierarchy (for example, a Site Manager can only add a Team Member or Visitor).

Building at Organisation/Brand/Site Level

As highlighted, there are items which can be built at organisation, brand, or site level. Such items include the Product Menu and Services. Once built, these items cannot be edited at a lower level. For example, if a HQ Manager adds a Product Menu at organisation level, it will appear for all sites but that menu cannot be edited by the Brand Manager or Site Manager at their respective level.

Login As

The senior users (HQ Manager, Brand Manager & Operations Manager) within DFS have access to the ‘Login As’ feature which allows them to login to a specific site which gives them access to be able to complete actions at Site Level.

Please note that we have the ability to choose which sites each user can login to and it could be set up so that a senior manager has no ‘Login As’ permissions. Further to this, we can also set the site permissions they have when they log in to the site. For example, we could set up one HQ Manager who can login to each site as a Site Manager, while another can login to each site as a Team Member.

The below user personas will describe what actions each role within the Navitas DFS platform is able to perform and will clearly display the differences between each role.

Visitor:

This is Toby, he’s our visitor on our site today so will only have access to the single site he’s visiting through his login. He will only be able to see the HACCP and Knowledge documentation, as well as the list of staff records.

Team Member:

This is Michael, he’s our Team Member and only has access to the one site he works within. He’s only responsible for his own/his sites tasks that need to be completed within the platform. To do this he will have the ability to complete the checklists/forms assigned to the site, enter the food temperatures he’s taken into the system and monitor the appliance temperatures to ensure none go into a non-compliant range. He will also be able to view the HACCP documentation and any other documentation specifically uploaded to the Knowledge module for his site.

Site Manager:

This is Angela, she’s our Site Manager and only has access to the one site she works within. Angela is responsible for all the Team Members within her site, ensuring all the due checklists/forms are completed, the food temperatures taken are compliant while resolving non-compliant food temperatures and monitoring that the appliances are compliant. As a Site Manager, Angela will also have the ability to edit/create/diarise forms, create new staff records, view site records, edit/create suppliers, edit/create appliances, create visitor accounts, as well as being able to add/remove documentation to the HACCP and Knowledge modules. Angela will be able to create reports from the system, she will be able to do this by selecting which information she would like to see within the report that is to do with her site only.

Operations Manager:

This is Erin, she’s our Operations Manager and has oversight, control and access of specific sites allocated to her. This means she has the ability to use the ‘Login As’ feature to login as any of the Team Members/Site Managers of the sites allocated to her. This is similar to Oscars role as Brand Manager however, Erin’s sites do not have to be restricted to one brand, they can be across multiple brands the organisation may have in place, giving her a wider range of access. She will still be able to go on and access the sites through the Team Member/Site Manager logins and use their individual level of access to view/edit the site however, she will be able to do this across multiple sites from her platform login.

Brand Manager:

This is Oscar, he’s our Brand Manager and has oversight, control and access to any sites under the single brand that he is assigned to. He has the ability to use the ‘Login As’ feature to login as any of the Team Members/Site Managers of the site(s) under his brand and carry out all the actions those roles enable by logging in as their account. This means Oscar will be able to view the platform and complete tasks when logging in as a Team Member as well as being able to login as a Site Manager to view and make edits on the platform from within their access level.

HQ Manager:

This is Kelly, she’s our HQ Manager and has access and control over the entire system, this means she has access to all brands, sites and users throughout the organisation and can view/edit each site by using the ‘Login As’ feature. She has the ability to do everything the other roles can do from her platform login and access the entire organisation's reports. Kelly’s login can only be made by Navitas Support Team as the HQ Manager roles are normally reserved for high level management.