User Rights for MaTaP Users - Revision history

LMA: /* PunchPoint User Rights */

2025-03-31T07:57:29Z

‎PunchPoint User Rights

REP: /* Available User Rights */

2025-03-26T12:46:45Z

‎Available User Rights

ARU at 12:54, 14 March 2025

2025-03-14T12:54:59Z

ARU at 12:51, 11 November 2024

2024-11-11T12:51:23Z

LMA at 11:50, 16 May 2024

2024-05-16T11:50:38Z

LMA at 08:11, 14 May 2024

2024-05-14T08:11:05Z

LMA at 11:25, 13 April 2024

2024-04-13T11:25:46Z

LMA at 12:08, 8 April 2024

2024-04-08T12:08:49Z

LMA at 11:26, 8 April 2024

2024-04-08T11:26:50Z

LMA at 10:08, 8 April 2024

2024-04-08T10:08:37Z

@@ Line 17: / Line 17: @@
 Selection:
 * No Right: The user cannot do anything related to PunchPoints.
-* Create PunchPoint: The user can create PunchPoints.
+* Create PunchPoint: The user can create new PunchPoints.
 * Issue PunchPoint: The user can create and issue PunchPoints.
-* Resolve PunchPoint: The user can create, issue and resolve PunchPoints.
+* Resolve PunchPoint: The user can create and issue PunchPoints. The user can resolve them if his company fits the PunchPoint's configured responsibility.
-* Accept PunchPoint: The user can create, issue, resolve and accept PunchPoints.
+* Accept PunchPoint: The user can create and issue PunchPoints. The user can resolve and accept them if his company fits the PunchPoint's configured responsibility.
-{{Hint|These rights are company-restrictive. These actions will only be enabled on Punchpoints within the user's own organizational group.}}
 === Reporting User Rights ===

@@ Line 1: / Line 1: @@
 For security and administration purposes, MaTaP allows configuring different access rights for users on the server. The client allows/disallows certain actions based on these configurations.
-== Available User Rights ==
+User rights are divided into two groups. 'Superusers' are system admins and therefore have all rights. Individual rights are assigned per user and usecase as described below.
-=== Super User Right ===
+{{Attention|Assigning Superuser rights overwrites any individually-assigned rights.}}
 If this is set to true:
 * The user can create, issue, accept and resolve PunchPoints.
 * The user can read and report progress without restrictions.
 * The user can create, issue, technical approve and financial approve ScopeChanges.
 === PunchPoint User Rights ===
 Selection:
@@ Line 14: / Line 21: @@
 * Resolve PunchPoint: The user can create, issue and resolve PunchPoints.
 * Accept PunchPoint: The user can create, issue, resolve and accept PunchPoints.
 === Reporting User Rights ===
 Selection:
@@ Line 20: / Line 29: @@
 * Company Restrictive: The user can read and report progress only for Data belonging to the users company.
 * Progress: The user can read and report progress without restrictions.
 === ScopeChange User Rights ===
 Selection:
@@ Line 27: / Line 37: @@
 * Technical Approve: The user can create, issue and technical approve ScopeChanges.
 * Financial Approve: The user can create, issue, technical approve and financial approve ScopeChanges.
 == Configuration ==

@@ Line 32: / Line 32: @@
 [[File:UserRights.png | 750px]]
 == Evaluation of User Right Groups ==
@@ Line 47: / Line 45: @@
 For the MaTaP Web Client context, the evaluation is slightly different. Here, user rights groups are loaded for all active projects; however, as with the other context, unused or unnecessary groups are not delivered to the client.
 [[Category:MaTaP|User Rights for MaTaP Users]]

← Older revision		Revision as of 12:51, 11 November 2024
Line 32:		Line 32:

	[[File:UserRights.png \| 750px]]		[[File:UserRights.png \| 750px]]
		+
		+	{{UnderConstructionStart}}
		+
		+	== Evaluation of User Right Groups ==
		+	Until now, the loading of user rights groups always included all groups, even those that were not used or required by the project. To ensure that unnecessary user rights groups are no longer loaded, two evaluators have been added. These evaluators analyze the user rights groups in the background for the specific MaTaP contexts and only deliver those user rights groups that are needed. There are two types of MaTaP-specific contexts: the first type is for the MaTaP Desktop Client, and the second is for the MaTaP Web Client. It should also be noted that the MaTaP Desktop Client may have multiple contexts, whereas the MaTaP Web Client uses only a single context.
		+
		+	The major advantage of this approach is that loading times are reduced, as the numerous user rights group instances that accumulate in the database over time are no longer delivered to the clients—only the groups actually needed are provided.
		+
		+	=== MaTaP Desktop Client Contexts ===
		+
		+	The evaluation for the contexts related to the MaTaP Desktop Client is such that only the user rights groups linked to the project are loaded.
		+
		+	=== MaTaP Web Client Context ===
		+
		+	For the MaTaP Web Client context, the evaluation is slightly different. Here, user rights groups are loaded for all active projects; however, as with the other context, unused or unnecessary groups are not delivered to the client.
		+
		+	{{UnderConstructionEnd}}

	[[Category:MaTaP\|User Rights for MaTaP Users]]		[[Category:MaTaP\|User Rights for MaTaP Users]]

← Older revision		Revision as of 11:50, 16 May 2024
Line 32:		Line 32:

	[[File:UserRights.png \| 750px]]		[[File:UserRights.png \| 750px]]
		+
		+	[[Category:MaTaP\|User Rights for MaTaP Users]]

← Older revision		Revision as of 08:11, 14 May 2024
Line 1:		Line 1:
−	~~{{Attention\|This page is under construction.}}~~
	For security and administration purposes, MaTaP allows configuring different access rights for users on the server. The client allows/disallows certain actions based on these configurations.		For security and administration purposes, MaTaP allows configuring different access rights for users on the server. The client allows/disallows certain actions based on these configurations.

← Older revision		Revision as of 10:08, 8 April 2024
Line 1:		Line 1:
−	For security and administration ~~purpose~~, MaTaP allows configuring different access rights for users on the server. The client allows/disallows certain actions based on these configurations.	+	{{Attention\|This page is under construction.}}
		+	For security and administration purposes, MaTaP allows configuring different access rights for users on the server. The client allows/disallows certain actions based on these configurations.

	== Available User Rights ==		== Available User Rights ==