Kordeus.PAX - User Roles
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
The Kordeus.PAX generally known these 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 :
- users may process and share their data fully indenpent of the portals/applications (see this data on b-op data handling )
- users access to an application makes sense on which operations they want to perform and to which data they have access.
Example: 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 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:
| 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) |