Roles and permissions

The mobileX-ServicePlatform allows you to control the visibility and editability of functions and data via roles and permissions. The permissions for individual functions and/or data are linked to roles, which you can assign to users.

System roles

System roles are roles that are defined by the system and combine several central permissions within the mobileX-ServicePlatform. System roles cannot be changed or deleted by the user. The following system roles currently exist in the mobileX-ServicePlatform:


  • has permission to create new resources and edit user-specific information e.g. role, plannability (this may affect the monthly user fee)

  • has permission to create individual roles (including permissions) in the system

  • has permission to retrieve all import and export protocols

Business administrator

  • has permission to make central, technical configurations for the system (e.g. administration of order types)

  • has permission to maintain master data in the system (e.g. creation of reference products, definition of attributes)


  • has permission to create and edit customers

Mobile User

  • receives access to the mobile app mobileX-CrossMIP and can thus receive and display orders and create operation confirmations

  • can also see orders assigned to them in mobileX-DispatchX

Individual roles

Individual roles can be created in addition to the system roles in the mobileX-ServicePlatform to allow processes and resources to be visible, editable and plannable. The basis for this are the attributes of the mobileX-ServicePlatform. Individual roles can be created and managed in the "Settings", section "Roles". The permissions of an individual user combine any permissions their assigned roles have.

Create Role

Individual permissions can be granted within a role. First, decide if the permission is applicable to resources or operations. Then, choose the attribute and (if you chose an attribute with values) its value(s). Finally, select which actions should be included. In the example below, a permission is created for the attribute "Qualifications" and the value "Electric". This means, users with this permission have the ability to view and plan resources with the qualification "Electric". When you wish to create a permission that applies regardless of attributes, you can use the placeholder "*".

Add Permission

The following example illustrates the role of a dispatcher who is responsible for planning the resources in Team South. The dispatcher has permission to see and plan all resources with the attributes "Team Nord" or "Team Ost". However, this role does not allow them to edit said resources (for example by changing their address). Additionally, they have permission to edit and plan all operations in the system (independent of any attributions).

Permissions Example