User Rights

Introduction

Information

Each user in PLANTA project has specific rights assigned to them. These determine which areas in the software are displayed and usable and which actions can be executed.

This topic addresses all users and answers the following questions:

Which navigation points are available to a user in the user menu, and what determines what a user sees?
Which objects is the user authorized to create, edit, or delete?
Which actions are permitted within a project?

The management and assignment of rights is handled by the administrator. In the separate documentation Rights Control, it is described how rights are configured.

Overview of the Authorization Concept

The authorization concept in PLANTA project is divided into three levels:

Level	Name	What Is Controlled?
Level 1	Module Visibility and System-Wide Authorizations	Which modules are visible and what system-wide authorizations exist
Level 2	Object Access and Multi-Client Capability	Which projects, portfolios, and resources are accessible
Level 3	Object Roles	Which actions are allowed within a specific project or portfolio

Level 1: Person Groups and Module Visibility

Every user is assigned to one or several person groups. The person group determines which navigation areas and modules are visible and which system-wide actions (e. g. creating a new project) are available.

Person groups

To control navigation, groups of people are defined in the first step, e.g.

Person group	Typical activities
Multi-project manager (MPM)	Manages across multiple projects and programs.
Project manager (PM)	Manages individual projects. Access to all project areas.
Employee (EM)	Only uses the personal area for entering their own hours worked. No access to projects or other modules.
Admin (ADM)	Manages the PLANTA configuration, users, and rights. Access to the administration area:

The navigation structure is fixed and independent of the rights. The navigation in PLANTA project is two-tiered:

Step	Element	Examples
Step 1	Navigation Area (Expandable)	Personal Area, Planning, Reports
Step 2	Module Groups (Module Panels)	Projects, Portfolios, Costs, Efforts

In a matrix it is determined which navigation point is visible to which person group:

Navigation point	MPM	PM	EM	ADM
Projects	✔	✔	✘	✘
My Activities / Time Recording	✔	✔	✔	✘
Administration	✘	✘	✘	✔
Reports	✔	✔	✘	✔

By assigning person groups to users, it is determined which navigation points the respective user sees in their user menu.

Each navigation point appears exactly once, even if multiple person groups are assigned. The visibility results additively from all assigned person groups.

System-Wide Rights

System-wide rights control the creation, editing, and deletion of planning objects.

The authorization to create planning objects is also controlled by the membership in person groups, the authorization to edit and delete is controlled by user parameters.

New planning objects can be created using the “+” button at the very top of the navigation menu. Only the options for which the corresponding authorization exists are displayed:

Level 2: Object Access

A second level controls which specific objects (projects, portfolios, resources) are visible to a user.

Purpose: This level makes sure that users of different departments or clients can only see the data relevant to their area.

Access to Projects and Portfolios

Which projects and portfolios are visible is determined by the structure code of the cost center assigned to the respective planning object and by the structure code area that is stored in the user profile. If the codes coincide the object is shown in analyses and lists.

If a project cannot be found even though there should be access to it, please contact your administrator, it is possible that the appropriate structure code assignment is missing.

Access to Resources and Skills

Similarly, a resource structure code controls which resources and skills are displayed and available for selection during planning. The configuration is done by the project management administrator in the user profile.

Level 3: Object Roles

Object roles determine which actions are permitted within the respective object, independent of the general person group.

What am I allowed to do in a project?

Object Role	What does this mean for me?
Project Manager	The project may be edited, configured, and assigned to other users for editing. Changing the functional ID, locking and unlocking, and deleting the project is not permitted. These actions are reserved for users with multi-portfolio and multi-project manager rights.
Project Staff	The project can be viewed and own actual hours can be recorded. Changing the project data is not permitted.
Stakeholder Area	The project can be viewed. Only read rights exist.
Stakeholder with Modification Rights	The project can be viewed and edited. This role corresponds to a deputy project manager.

Roles are assigned by the project manager of the project, a multi-project manager, or the administrator.

Example

Anna has the Project Manager person group and her structure code corresponds to the cost center of the project, and yet she is not authorized to edit it, because her object role in this specific project is only “project staff”.