Case security
Case types can be secured on the case type form Admin Workspace > Case Types.
|
•
|
The Assigned To user as well as Users in the Notification role, Escalation Level 1 or Escalation Level 2 roles always have rights to the case regardless if it is a secure case type. |
|
•
|
If the Secure option is cleared on the Case Type, then any Internal User with access to cases has access to that Case Type. If it is selected, only those users and Global Admins have access to that Case Type. |
|
•
|
When the Case Type is secured, the system generates a CaseType_#TypeName# security entity that can then be used to provide secure case type access to users other than those directly associated with the case type (see above). So, if the Case Type of Client Payrolls was secured, the system would generate a CaseType_ClientPayrolls entity that could then be added to a role to provide secure access to cases of that type. |
|
•
|
Secured Case Types implement Row (or record) Level Security, meaning that when the case is generated, security roles are generated for the user roles mentioned previously, for that individual case using the role values on the case type at the time. |
|
•
|
Making a Case Type secured, or changing the roles associated with that security will only affect newly created cases going forward from the time of the change. Likewise, removing case type security does not remove security on the previously created cases of that type. |
|
•
|
Global Admins can click the padlock icon in the header of an individual Case to remove record level security for individual cases. |
|
•
|
Users that have the client service case entity with a level of access of Admin will be able to access secured cases with row level security via notifications or BI reports. They will not be able to see these cases in the Case module by default and will only be able to link to them from the methods mentioned before. |