Module level security Ist Level Security

---

Module Level Security is used for setting access levels of users, in terms of their ability to manipulate data. Module security can be set from the "Modules" tab of the "Settings" screen, within the "Admin Control Panel". Click Edit for the module you wish to set security settings for.

The example below will illustrate the steps invloved in specifying  the security settings for the Job module.

1. Start by clicking the "Edit" button on the jobs module

2. Click on the "Security" tab

Now you are able to set access permissions for Users and well as Path Groups ( a set group of users).

3. Under "Permissions",  click on the [Add] button.

4. A search screen should now appear, you may now search/select specific Users or Path Groups in which you want to set access rights for.

5. Assuming that you have selected a User of the system ( by ticking the check box next to ther user, and pressing [Ok] )

You should now see an array of pick lists, as described below:

Note: The options available from the pick lists are "Allow" and "Deny" or left blank:

• Full Control: When "Allow" is selected it will enable the User full access of the module.
• Create: Allows you to create new instances of the module, e.g. creating new jobs
• Read: Allows Users to view the instances of module only, 
• Modify: Allows the User make changes to the instances of module, e.g. editing the status of jobs
• Delete: Allows the User to delete instances created within the module, e.g. creating new jobs.
  

Default Settings:

• "Deny" conditions will always be read by the system first before "Allow" conditions.
  
• It is important to note that by setting "Allow" for a particular modules, it would mean that only that particular User would have access to the option selected, other Users will NOT. For example, when "Allow" is selected for the "Create" Pick List in the jobs module, for a particular User. This would mean that only the Users selected will be able to create instances of the jobs modules, other users will be denied access.
• The above example will also apply the "Deny". So when "Deny" is set for one user, all users will be denied access to a particular module. This is beacause if one user is denied access,  we cannot asssume that other users are given automatic access. 
  
• Following on from above, if you would like other users to have have the ability to delete, you may either choose another User and select "Allow", or you may select Allow for a Path Group.
  

Note: By default all Users will have access to the data stored within Super-Tracker.

If you are part of the everyone group, the "Deny"  will always be accessed first. In addition, if "Allow" is selected within the pick lists, then the entries left blank would be defaulted to "Deny".

What  are Path Groups?

By definition a Path Group is a list of Users that have a list of common responsibilities or positions. An example of a path group would be  "Purchase Order: Sales Person", this would identify all Users of the system whom are identified as a Sales Person.

What are System Groups?

A System Group is a group of Users of the system that has a common level of access. There are 4 distinct access levels within Super-Tracker, they include:

Owner: A person who has the ability to assign tasks to other Users,  and modify the settings of Super-Tracker within the "Admin Control Panel" tab.
Public: A person who may only view certain data contained within Super-Tracker
Root: A person that may modify the internal structure, and the functionality of Super-Tracker.
User: A person who may have limited access righst within Super-Tracker, for example they do not have the ability to modify the system settings.

Default System Groups within Super-Tracker includes, "Everyone", "Owner" and "User"