Profile Configuration Manual

User types are a high level way of defining the user privileges. They allow individual access settings to be grouped together.

To view the user types:

Select 'User Types' from the 'Admin' menu.

User Types

To add a new user type:

Select 'User Types' from the 'Admin' menu.
Click 'Add'

User Types

Specify the fields as follows:

Field	Description
User Type Name	This is the name that will identify the user type eg "Technician". "Operator" or "View Only" etc.
Group	Select the application group that the access levels will apply for. Once the group is selecte it will display a list of access permissions associated with that group. A user type record only covers a single group but user types can be set up to over multiple groups and the user type name can be reused across these groups. ie a user type "Technician" can be created in both the Record™ and Profile™ groups.
Permissions	To give the permission to the user type, tick the corresponding checkbox. Changes to permissions for the user type affect all users who have been assigned that user type.

User Permissions

Profile offers the following permissions which can be applied globally or on a site by site basis:

Permission	Description
Edit RTU	This permission controls who can make changes to the RTU details.
View Alarms	This permission controls who can see alarms.
Accept Alarms	This permission controls who can accept alarms (although the user must also have the View Alarms permission enabled).
Edit Level n	This permission controls who can access which level of field in the RTU. Each field has a security level assigned to it. These security levels for the fields are defined in the configuration. Anyone with a corresponding edit level can make changes to the value of that field in the RTU. Fields with a security level zero can never be edited. A user will only be presented with an edit button on a screen if their edit level matches the security level and the security level of the field is not zero. Users can be assigned non-contiguous levels of edit access eg 1,3,6,8, but unless there are special requirements to lock access to certain fields, you would normally enable all edit level permissions for users with rights to make changes to an RTU.
View Level n	This permission controls who can view fields on a screen and even view the screens themselves. Every screen and field on a screen can be allocated a view level. Anyone with access to a site can view a screen / field with a view level of zero. View levels for the screens / fields are defined in the configuration. If a user does not have the necessary view level for a screen, they will not be able to see the screen at all in their screen list. If a user does not have the necessary view level for a field, they will still be able to see the screen (as long as they have access to that screen) but they will not be able to see the field on the screen. View levels for screens and fields can both be set individually to provide a high level of control of what a user can see. Eg a user may be able to view a screen with view level 1 but then cannot see fields with view levels that have been assigned to be 3. Normally you would enable all view level permissions for most users.