Kordeus.PAX - User Roles - Revision history

Stefanseiler: /* Roles and Portal Binding */

2026-04-30T10:36:36Z

Roles and Portal Binding

← Older revision		Revision as of 10:36, 30 April 2026
Line 31:		Line 31:
	!		!
	! User-Groups / Roles		! User-Groups / Roles
	![[:Category:Digital Types\|Digital Type]]		!Data owning
			[[:Category:Digital Types\|Digital Type]]
	! Comment		! Comment
	\|-		\|-

Stefanseiler: /* Parties / General Roles */

2026-04-30T10:35:51Z

Parties / General Roles

← Older revision		Revision as of 10:35, 30 April 2026
Line 30:		Line 30:
	{\| class="wikitable"		{\| class="wikitable"
	!		!
	! ~~Role~~		! User-Groups / Roles
			![[:Category:Digital Types\|Digital Type]]
	! Comment		! Comment
	\|-		\|-
	! PAX.Portal		! rowspan="2" \| PAX.Portal
	\| Passenger~~, Travel Partner Staff~~		\| Passenger
			\|[[Passenger digitals\|Passenger]]
	\| LH PAX Portal, Discover PAX Portal		\| LH PAX Portal, Discover PAX Portal
	\|-		\|-
	! SARA		\|Travel Partner Staff
	\| MOC Staff, Doctors		\|[[Travel partner digitals\|Travel Partner]]
			\|
			\|-
			! rowspan="2" \| SARA
			\| MOC Staff
			\| rowspan="2" \|[[Travel assistance service operation center digitals\|Medial Operation Center]]
			\|
			\|-
			\|Doctors
	\|		\|
	\|-		\|-
	! DeliveryPartner.Portal		! DeliveryPartner.Portal
	\| Delivery Partner Staff		\| Delivery Partner Staff
			\|[[Delivery partner digitals\|Delivery Partner]]
	\|		\|
	\|-		\|-
	! Core.Admin		! Core.Admin
	\| System Administrators / Core Admins		\| System Administrators / Core Admins
			\|[[Carrier digital\|Carrier Digital]]
	\| LH Group Digital (LH/Discover)		\| LH Group Digital (LH/Discover)
	\|}		\|}

Stefanseiler at 07:21, 30 April 2026

2026-04-30T07:21:55Z

← Older revision		Revision as of 07:21, 30 April 2026
Line 1:		Line 1:
	Kordeus.PAX is a distributed process guidance system ~~which~~ governs interactions between ~~various~~ parties~~, each owning their~~ own b-op Digitals ~~as part of the~~ highly distributed ~~Peer~~-To-~~Peer~~ network.		'''Kordeus.PAX''' is a distributed process guidance system that governs interactions between multiple parties. Each party owns its own b-op Digitals within a highly distributed peer-to-peer network.

	=== Parties / General Roles ===		=== Parties / General Roles ===
	~~The~~ Kordeus.PAX generally ~~known these~~ roles:		Kordeus.PAX generally distinguishes between the following roles:
	* Passenger
			* Passenger
	* Travel Partner Staff		* Travel Partner Staff
	* MOC Staff		* MOC Staff
Line 10:		Line 11:
	* Core Admin		* Core Admin

	=== Roles and Portal ~~binding~~ ===		=== Roles and Portal Binding ===
	Kordeus.PAX <u>is not</u> ~~an old fashion~~ monolithic "'''one-software fits all roles'''" ~~& "'''all data are in on~~ large database~~'''" system~~. Instead :		Kordeus.PAX <u>is not</u> a traditional monolithic system based on a "'''one software fits all roles'''" approach or a single large central database. Instead:

			* Users can process and share their data independently of specific portals or applications. For further information, see [[KORDEUS - Data retention and deletion concept\|b-op data handling]].
			* User access to an application depends on the operations they need to perform and the data they are authorized to access.

			<u>Example</u>: It would not be meaningful for ground handlers to access the PAX.Portal to manage their tasks. In addition, PAX.Portal does not provide this functionality.

	* users may process and share their data fully indenpent of the ~~portals/applications (see this data on [[KORDEUS - Data retention and deletion~~ concept~~\|b-op data handling]] )~~		As a result, the traditional role concept within a single application is less dominant than in conventional applications:
	* users access to an application ~~makes sense on which operations they want to perform and to which data they have access.~~
	~~<u>Example</u>~~: ~~it does not make sense for ground handler to access the PAX.Portal for managing their tasks. Besides that the PAX.Portal does not even offer this functionality!~~

	So the ~~classical role concept~~ with ~~an application~~ is no ~~longer as dominant as it was in old fashioned applications:~~		* Each application is one of several possible interfaces through which data owners can manage their data.
			* Applications act as '''access gateways for data-driven actions'''.
			* Data residency and ownership are decoupled from the physical location of the application. Each application supports a defined set of operations and data processing actions.
			* Interaction with other Digitals is governed by established trust relationships. If no trust relationship exists, the corresponding operations are blocked.

	* Each application is ~~just one of possibility of mulitple~~ for data ~~owners to manipulate~~ the ~~owners data~~.		Accordingly, the use of specific portals is only relevant for roles that own or process data within the respective application. The following table shows the role-to-portal mapping for '''Kordeus.PAX''':
	* Applications act as '''~~access gateways to data-driven actions~~'''.
	* Data residency and ownership is being totally dissolved from the physical residency of the application. So the application has a set of possible operations / data processing actions it supports.
	* Interaction with other digitals is defined by established trust relations. So non-existing trust relations also block operations.

	~~Instead usage of specific portals only makes sense for roles, which own data to process in that application. Here is a role to portal map for '''Kordeus.PAX''':~~
	{\| class="wikitable"		{\| class="wikitable"
	!		!
	!Role		! Role
	!Comment		! Comment
	\|-		\|-
	!PAX.Portal		! PAX.Portal
	\|Passenger, Travel Partner		\| Passenger, Travel Partner Staff
	\|LH PAX Portal, Discover PAX Portal		\| LH PAX Portal, Discover PAX Portal
	\|-		\|-
	!SARA		! SARA
	\|MOC Staff, Doctors		\| MOC Staff, Doctors
	\|		\|
	\|-		\|-
	!DeliveryPartner.Portal		! DeliveryPartner.Portal
	\|Delivery Partner		\| Delivery Partner Staff
	\|		\|
	\|-		\|-
	!Core.Admin		! Core.Admin
	\|System Administrators / Core Admins		\| System Administrators / Core Admins
	\|LH Group Digital (LH/Discover)		\| LH Group Digital (LH/Discover)
	\|}		\|}

Stefanseiler: /* Roles and Portal binding */

2026-04-30T07:20:16Z

Roles and Portal binding

← Older revision		Revision as of 07:20, 30 April 2026
Line 11:		Line 11:

	=== Roles and Portal binding ===		=== Roles and Portal binding ===
	Kordeus.PAX <u>is not</u> an old fashion monolithic "'''one-software fits all roles'''" & "'''all data are in on large database'''" system. Instead ~~each user has~~:		Kordeus.PAX <u>is not</u> an old fashion monolithic "'''one-software fits all roles'''" & "'''all data are in on large database'''" system. Instead :

	* users may process and share their data fully indenpent of the portals/applications (see this data on [[KORDEUS - Data retention and deletion concept\|b-op data handling]] )		* users may process and share their data fully indenpent of the portals/applications (see this data on [[KORDEUS - Data retention and deletion concept\|b-op data handling]] )
	* users ~~get~~ access to ~~portal by~~ their ~~roles~~.		* users access to an application makes sense on which operations they want to perform and to which data they have access.
			<u>Example</u>: it does not make sense for ground handler to access the PAX.Portal for managing their tasks. Besides that the PAX.Portal does not even offer this functionality!

	So the classical concept ~~is turned upside down. Not the application determines the roles, but the role determine application access. The~~ application is ~~just a pathway to perform certain operations with data residency and ownership being totally dissolved from the place of the application.~~		So the classical role concept with an application is no longer as dominant as it was in old fashioned applications:

	~~<u>Example</u>: it does not make sense~~ for ~~ground handler~~ to access the ~~PAX~~.~~Portal for managing their tasks~~		* Each application is just one of possibility of mulitple for data owners to manipulate the owners data.
			* Applications act as '''access gateways to data-driven actions'''.
			* Data residency and ownership is being totally dissolved from the physical residency of the application. So the application has a set of possible operations / data processing actions it supports.
			* Interaction with other digitals is defined by established trust relations. So non-existing trust relations also block operations.

	Instead usage of specific portals only makes sense for roles, which own data to process in that application. Here is a role to portal map for '''Kordeus.PAX''':		Instead usage of specific portals only makes sense for roles, which own data to process in that application. Here is a role to portal map for '''Kordeus.PAX''':
	{\| class="wikitable"		{\| class="wikitable"
	!~~Access Gateway~~		!
	!Role		!Role
	!Comment		!Comment

Stefanseiler: /* Roles and Portal binding */

2026-04-30T07:10:12Z

Roles and Portal binding

← Older revision		Revision as of 07:10, 30 April 2026
Line 22:		Line 22:
	Instead usage of specific portals only makes sense for roles, which own data to process in that application. Here is a role to portal map for '''Kordeus.PAX''':		Instead usage of specific portals only makes sense for roles, which own data to process in that application. Here is a role to portal map for '''Kordeus.PAX''':
	{\| class="wikitable"		{\| class="wikitable"
	!~~Portal~~		!Access Gateway
	!Role		!Role
	!Comment		!Comment
	\|-		\|-
	\|PAX.Portal		!PAX.Portal
	\|Passenger, Travel Partner		\|Passenger, Travel Partner
	\|LH PAX Portal, Discover PAX Portal		\|LH PAX Portal, Discover PAX Portal
	\|-		\|-
	\|SARA		!SARA
	\|MOC Staff, Doctors		\|MOC Staff, Doctors
	\|		\|
	\|-		\|-
	\|DeliveryPartner.Portal		!DeliveryPartner.Portal
	\|Delivery Partner		\|Delivery Partner
	\|		\|
	\|-		\|-
	\|Core.Admin		!Core.Admin
	\|System Administrators / Core Admins		\|System Administrators / Core Admins
	\|LH Group Digital (LH/Discover)		\|LH Group Digital (LH/Discover)

Stefanseiler: /* Parties / General Roles */

2026-04-30T07:09:28Z

Parties / General Roles

← Older revision		Revision as of 07:09, 30 April 2026
Line 2:		Line 2:

	=== Parties / General Roles ===		=== Parties / General Roles ===
			The Kordeus.PAX generally known these roles:
	* Passenger		* Passenger
	* Travel Partner Staff		* Travel Partner Staff

Stefanseiler: Created page with "Kordeus.PAX is a distributed process guidance system which governs interactions between various parties, each owning their own b-op Digitals as part of the highly distributed Peer-To-Peer network. === Parties / General Roles === * Passenger * Travel Partner Staff * MOC Staff * Doctors * Delivery Partner Staff * Core Admin === Roles and Portal binding === Kordeus.PAX is not an old fashion monolithic "'''one-software fits all roles'''" & "'''all data are in on l..."

2026-04-30T07:09:06Z

Created page with "Kordeus.PAX is a distributed process guidance system which governs interactions between various parties, each owning their own b-op Digitals as part of the highly distributed Peer-To-Peer network. === Parties / General Roles === * Passenger * Travel Partner Staff * MOC Staff * Doctors * Delivery Partner Staff * Core Admin === Roles and Portal binding === Kordeus.PAX is not an old fashion monolithic "'''one-software fits all roles'''" & "'''all data are in on l..."

New page

Kordeus.PAX is a distributed process guidance system which governs interactions between various parties, each owning their own b-op Digitals as part of the highly distributed Peer-To-Peer network.

=== Parties / General Roles ===

* Passenger
* Travel Partner Staff
* MOC Staff
* Doctors
* Delivery Partner Staff
* Core Admin

=== Roles and Portal binding ===
Kordeus.PAX is not an old fashion monolithic "'''one-software fits all roles'''" & "'''all data are in on large database'''" system. Instead each user has:

* users may process and share their data fully indenpent of the portals/applications (see this data on [[KORDEUS - Data retention and deletion concept|b-op data handling]] )
* users get access to portal by their roles.

So the classical concept is turned upside down. Not the application determines the roles, but the role determine application access. The application is just a pathway to perform certain operations with data residency and ownership being totally dissolved from the place of the application.

Example: it does not make sense for ground handler to access the PAX.Portal for managing their tasks

Instead usage of specific portals only makes sense for roles, which own data to process in that application. Here is a role to portal map for '''Kordeus.PAX''':
{| class="wikitable"
!Portal
!Role
!Comment
|-
|PAX.Portal
|Passenger, Travel Partner
|LH PAX Portal, Discover PAX Portal
|-
|SARA
|MOC Staff, Doctors
|
|-
|DeliveryPartner.Portal
|Delivery Partner
|
|-
|Core.Admin
|System Administrators / Core Admins
|LH Group Digital (LH/Discover)
|}

== See also ==

* [[Kordeus.PAX]]