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 each user has:

• users may process and share their data fully indenpent of the portals/applications (see this data on 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:

Access Gateway	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