Security Framework

Security means that the information is protected from unauthorized users. Security also encompasses the concept of integrity, that is, the assurance that information is protected from unauthorized modification or corruption.

In an organization, a security policy is how an organization plans to protect the information from the employees who are categorized based on their designations or roles. The security rights provided to different users depend on the organizational hierarchy.

The need for security is to assign access rights to this hierarchy. If there is no hierarchy in the organization, then there would be no need for a assigning security rights. But most organizations have many hierarchies that have different access rights. The security mechanism in the organization provides restricted access to data. By making access decisions, the security mechanism enforce rules about who can access what.

For example, an administrator and a developer cannot have the same access rights, because obviously, the administrator is superior and has access to most or all of the rights. Similarly, an employee with a higher designation, say a Project Manager, should ideally have more rights as compared to a Team Lead. It is for this very purpose that access rights have to be clearly defined.

AVEVA Work Tasks Security

AVEVA Work Tasks has enterprise rights and security features. The rights and security can be defined for groups and users can be mapped to these groups. The user will be entitled to perform only those tasks for which the right has been given to the respective user.

AVEVA Work Tasks allows effective collaboration during workflow creation and process and allows you to define user-based access rights for workflow design functions. You can define security for the items, forms or folders at the list level and also define security for the forms or lists residing under a folder. It also offers comprehensive security for reporting Work item, Calendar, Queue, and BAM.

The Security Framework allows the administrative user to administer, manage and provide access rights and define roles and responsibilities for the user, based on their individual role or based on the ‘group’ they are part of. It makes managing users across various features of AVEVA Work Tasks much easier and makes applications more secure.

AVEVA Work Tasks Security provides all the features for implementing security at different levels for users and groups and has in-built security groups and rights, which can be extended and customized.

AVEVA Work Tasks Security Features

The following are the features of AVEVA Work Tasks security:

1. AVEVA Work Tasks security has pre-defined security groups. These groups can be used to provide access rights to roles or users. Users can create new security groups if required.
   For example, map a user who belongs to HR to one group and map a user who belongs to Finance to another group. This allows them to view only the items or folders related to their work inside the list.

2. AVEVA Work Tasks security has a set of pre-defined rights. For example, Can Consume Item, Can Manage Item, Can Create Item.

3. There are mainly three levels where security can be applied. They are- Repository Level, List Level and ListItem Level. The List level security allows you to secure the access to various lists available in a AVEVA Work Tasks Repository. The ListItem level security settings allow you to secure the access to various items available in a list.

4. AVEVA Work Tasks security allows the user to secure the Process Designer. This can be done by providing security to its elements as mentioned below:

   1. Provide security for each Category, Action, and Property to ensure that only the authorized user is able to access each of these elements.

   2. Provide security for each menu item to restrict the users for each action on the design. For example: Importing or Exporting workflows, validating and publishing them, settings, running the wizards, testrun.

5. AVEVA Work Tasks security allows you to secure the work items. This can be done by restricting whether a user can forward or kill work items, can set an alternate actor or preferences, can view resource calendar, and queue.

6. AVEVA Work Tasks security allows you to secure the Queue. This can be done by restricting whether a user can view the queue control, add a new queue.

7. AVEVA Work Tasks security allows you to secure the Calendar control: Restricting whether the user can view, add, delete Calendar.

8. The user can exclude options from the Enterprise Console menu. Options like Inbox, Workflows, Reports, Fill Form, Tools (Manage Forms, Manage List) and Settings (User, Calendar, Queue) can be excluded.

Example: An organization has 'Manager', 'Designer', 'Technical Consultant', 'Employee', 'Finance team', 'HR team', 'Support team', and 'Other User' roles.  These roles having the following responsibilities:

• Manager - Monitor the representatives' reports

• Designer -  Design workflows and assign task to others

• Technical Consultant - Create lists and forms

• Employee - Fill forms created by the Technical Consultant and design cases

• Finance team - Fill and view only finance related lists

• Support team - Work on the assigned task

• HR team - Fill and view only HR related lists

• Other User - Create only forms or lists.

In the above case, security can be used to exclude various options from the Enterprise Console menu.

The Support team should have access only to the Inbox option, so that they can act only on the work items assigned to them.

The Designer should have access the Inbox and Workflows options, so that these users can design workflows, assign the tasks to some other user to act on the assigned work items.

The Technical Consultant should have access only Manage Forms and Manage Lists, so that these users can design

list or forms. For example, 'Expense List', 'Manage List', 'Leave Application List' and 'Travel List'.

The Employees should have access to only the Fill Form option, so that these users can fill forms like 'Leave List', 'Expense List' and 'Travel List'.

The HR team should have access only to the Workflows option, so that these users can view only HR related workflows. For example, 'Employee Details' and 'Leave Application List'.

The Finance team should have access only to the Workflows option, so that these users can view only Finance related workflows. For example, 'Expense List' and 'Travel List'.

The Manager should have access only to the Reports option, so that the manager can access reports. This user does not design any process and  only monitors the representatives' reports.

Other users should have access only to the Manage Forms or Manage List option, depending on whether they are responsible for designing the forms or for designing lists.