When setting up software security within your business, you will need to closely consider your organisational structure, workflow and employee usage requirements. Jim2 is designed as a multi-user application and, although allowing all users to have high level or unrestricted access to all functions may be appropriate in a small business, larger sites will probably want to limit employee work functions by using the security options available.
 |
If users are well trained on the interactive and flow-on effects of changes that they can make to existing defaults within Jim2, the level of security that management will need to implement will be reduced. If users receive a security warning, the administrator should be made aware of the sequence of events that caused it, and provide additional training to the user or change that user's security settings, as appropriate.
Security should be used to complement the Options, Setups and automated warnings that Jim2 already has in place. Setting security measures to restrict access to Jim2 functions should be done to prevent untrained users from performing functions, or pre-empting accidental data changes in areas that are particularly sensitive to your workflow. |
|
There are some functions which have a roll-on effect when selected as secured areas. For example, if you nominate that a security group can't view jobs, then that group won't be able to view a list of jobs. As such, you should familiarise yourself with the interaction of Jim2 objects prior to setting up security, or seek advice from a trained Jim2 consultant.
Within Jim2, security level or access is identified by security groups, tags and categories. Each employee can belong to more than one security group, tag or category, and has access rights to certain areas and functions within Jim2 that have been set up for those particular security groups, tags and categories.
When reports are devised, they are identified by ascending report levels – the higher the number, the more sensitive the company information that the report contains. Security groups must include an appropriate report level.
There are a large number of functions within Jim2 that can be restricted from use by using security. You have the option of allowing or denying any user or group the right to access any or all of those functions. |
 |
When setting up Jim2 for the first time, there is a default user called sys, with a password of sys. The sys user belongs to the security group of Administrator, thereby always giving sys access rights to set and edit security groups. Jim2 prevents the sys security group and card code from being changed, ensuring that there is always the option to set and edit security groups, in case access to security is accidentally set as denied to all other users. Once you have set up card files for other users with a security group of Administrator, it would be wise to change the default password of the user sys (via the User tab in the card file for sys), as this default password is commonly known. This will prevent users from logging on as sys and changing security options. |
|
All new security settings are active (enabled) in all security groups, until edited. |
Further information: