System rights for the task management module

System rights affect the options and actions available to workers

• Basic User Right – tskEverybody
• Experienced User Right – tskPowerUser
• Group Administrator Right – tskAdmin
• Right of the reader – fullread
• Right to participate in discussions – tskDiscussionPublic
• You may be interested

Note: Read more about system rights here.

System rights are set by the system administrator within the system groups. For more about system rights in general, see the system documentation here. This page is intended for system administrators.

Basic User Right – tskEverybody

Every user must have a right to work with the module. Without it, no module features and data are available in real or available.

Experienced User Right – tskPowerUser

An experienced user has the ability to use some features that the user is supposed to be careful about what they do. The right is important for executives, as some features for project managers and departments are limited by this right.

Activities tied to this right include:

• View roles and groups (it's not about managing them – it requires permissions from sys
• Definition of SLA contracts for helpdesk user and customer support
• Advanced project management tools – planning and working with baselines
• Working with methodologies and quality management system
• Checking documentation packages and managing project configuration management
• User area management
• Settings for synchronizing analytical models with Enterprise Architect

Group Administrator Right – tskAdmin

A group administrator has the right to change the personnel responsible for business area, corporate methodology, corporate address book or project.

An administrator's right gives the option of full management of areas and projects, but does not give the right to inspect those areas. This right does not give the staff access to specific data (except the managers).

Right of the reader – fullread

The special right allows you to inspect areas and projects without including them in their teams.

Specifically, the right is for audits, quality control or top executives.

Right to participate in discussions – tskDiscussionPublic

The right makes general discussions available. It makes sense for internal staff, on the contrary, it should not be given to external staff if we do not want to allow them into internal discussions.
By default, the tskDiscussionPublic right is part of the rights package for internal staff. If you want to restrict access to e-mail external staff, give them only basic rights (everybody).

• More about internal discussions.
• More about internal discussion security is here.

You may be interested

System permissions of the AyMINE framework
System permissions of the Order Management module
System permissions of the persoalistics module