The following explains how the security model is designed in Insolvency.
Security permissions are split into job-level access permissions and application-level access permissions.
These permissions allow users to perform work flows within a job.
Permissions grant a user the ability to perform a task or access a particular area. See the security matrix for an explanation of each individual permission.
A role provides a set or group of permissions that allows a user to perform a particular work flow. By allocating a user to a role, the user is linked to a defined set of permissions. For example, roles include managers, cash book operators or claim adjudicators and allows a user to perform all tasks associated with this role.
The software comes pre-loaded with system roles that have pre-defined permissions representing the standard access rights (provided as a template) for user access.
To set up job-level permissions see:
Provide an efficient way of managing permissions. Work teams are a team of users with specific roles. The work team can be assigned to a job as either a main work team or a linked work team.
Stand alone roles
Provide a single access right to access a single feature on a single job.
These permissions allow elevated levels of permissions for administrators to configure and administer the software.
Is a central role used to administer counterparties.
The Counterparty Administrator can Add, Edit, Edit the centralised counterparty database. You may update details including the bank accounts and maintain counterparties by merging duplicates counterparties. This application level role takes precedence over any counterparty roles selected under Job Security Roles.
Use this role to approve "Authorised suppliers" and/or "enter bank details". Separate this role from cashiers that are entering payments or uploading payment files to the bank.
This application-level role will allow one-time access to add a new job and set the security permission in the context of the job set up wizard.
This role gives complete access to perform all functions for all jobs, except those Actions under the Bank Group. Banking Group actions must be assigned to a role a user is assigned to. We do not recommend this method of access because you will not be able to separate duties which you would ordinarily be required to do to ensure a user doesn't commit fraud.
System admin rights. Full access to all permissions on all jobs in all practices. Again however the exception is those Actions under the Bank Group. Banking Group actions must be assigned to a role a user is assigned to. Administrator rights also includes full access to manage systems functions such as Manage Static Data, Manage Task Templates etc.
Task/Document Template Administrator
Access to Manage Document Templates and Manage Task Templates. Does not provide any access to jobs.
Also see: How to make a user inactive
Also see: How to update User roles in bulk