6. Role Management

For our process, we have identified the following roles and user. The names are fantasy names in order to protect the personal credentials of the employees of mimacom.

Permissions

All users should only have access to what they need to do their job effectively. All users except the head of the mandate have only access to the tasklist application.

Employees, Service Desk and billing personnel have access to two filters that show them their own attributed jobs and the ones they can claim because no-one in their group has already claimed them.

Head of the mandate needs to have the possibility to intervene and take over at any step of the process. That is why they have much more permissions. They are process owners.

Process Role	Description	Tasklist	Users
Head of Mandate	Employees with the mandate to control the reported times.	READ, START, EDIT	Bob Squarepants, Patrick Star, Mr. Krabs
Employee	Employee who reports the time	READ	Snail Garry, Squidward Tentacles, Planktion, Sandy Cheeks, Mrs. Puff,
Service Desk	Service Desk employee who checks the spelling.	READ	Flying Dutchman
Billing	Accounting Department of Mimacom.	READ	Pearl Krabs

Definitions:

Tasklist	Definition
READ	User has the possibility to open, read and change or input needed information in the task. However, the user has no possibility to change the structure of the process or task neither can he trigger new instances of the processes
START	with the "START" permission, this is the only person who can trigger new instances of the process.
EDIT	employees with editor permission can make changes. Because they are the process owner they can "take over" a task held by somebody else to move it forward (i.e. the person is on vacation)

Automatic default permission

At every fresh deployment, all authorizations for the default groups and users are applied against the system. All information is in this class AuthorizationGenerator.java