System rights

System rights provide blanket access to system functionality

This page is intended for system administrators.

• What system rights are for
• The meaning of system rights is limited
• Who and how system rights are set
• Detailed right settings

What system rights are for

System rights, or system rights and technically rights, allow you to define which system features a user may or may not use.

Examples of system rights:

• The right to create and manage users
• The right to join discussions
• The right to work with assets
• The right to allow the publication of news on the web
• The right to view all business areas on the system

The meaning of system rights is limited

Although the system defines over 100 different system rights, the vast majority of rights on the system are not governed by them. Listed above are a few special rights – such as the right to change the rights of others – for which system control is necessary. However, with the exception of a few administrators, the vast majority of team members or workers have exactly the same system rights. Yet the system strictly controls the rights. But otherwise.

The main weight of control is not on functionality, but on data. For example.

• The right to see tasks in project P
• The right to assign tasks to people in the C team
• The right to delete information created by a colleague K

All of these rights are governed by the right settings for a particular data area – business area, project, methodology, etc. System rights are completely secondary to this:

• System right allows me to work with information (probably everyone is allowed to do that)
• The rights on the area where the information is determines whether I am allowed to delete that particular information
• The information itself may have a lock that allows only the author to delete it

Managing system rights is therefore a fairly peripheral matter of system-wide administration. It is typically only done when starting a new company

Who and how system rights are set

By default, system rights are bundled into logical groups from system installation onwards, which make system functions available. These are called system roles, e.g.:

• All task module users – tsk everybody
• Common users of the assets module – am everybody

These system rights are assigned to people by the administrator. However, because it is inconvenient and unnecessary to assign system rights to everyone individually, it is more appropriate to

• Create one user group for all users – e.g. All employees
• Assign system roles to the group for everyone – this assigns the necessary system rights
• Assign the group to everyone

Detailed right settings

Caution: Only system administrators can make the settings described below. It is not even allowed for user account administrators.

The system also allows direct setting of system rights by

• The administrator gets temporary system rights frmAdmin
• Creates primary system right groups within the company/client space
• Assigns the necessary system rights to the primary groups. The simple way to do this is to copy the rights from the system roles and then modify the list individually
• The frmAdmin role is then removed.

Important remarks:

• Changes require all users to log out and log in afterwards. It is not safe to make changes to the system while it is running
• frmAdmin is a right that only a system administrator (superadministrator) can make. However, he must also grant it to the account that belongs to the client whose settings are being changed.