- Created by Annegret Bernhardt, last modified on Mar 28, 2023
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 5 Current »
The Portal is the starting point for all users of Scheer PAS. The content of the portal can be defined by a User Management administrator individually for each user. The user is shown only the tiles for the Scheer PAS components for which the administrator assigned him rights. The permissions on some components are also divided into "normal user" rights and extended admin rights. The following table gives an overview on all Scheer PAS standard profiles.
The profile pas_base is mandatory as it grants access to the Scheer PAS Portal , the entry into the platform.
Single Sign-on is available throughout all platform components: Log in once, and use all Scheer PAS components that are configured for your user.
Administrator Profiles
The following list of admin profiles can be searched: Use the available filter fields.
Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.
The table is being loaded. Please wait for a bit ...
Portal Tile | Profile | Description | Further Information | PAS Version |
---|---|---|---|---|
administration_user |
| PAS 21.1 | ||
xuml_container_admin |
| PAS 22.1 | ||
analytics_admin |
| |||
api_management_admin |
| PAS 21.1 | ||
keycloak_user |
| PAS 21.1 | ||
kibana_user |
| PAS 21.1 | ||
pas_admin_user |
| PAS 21.1 | ||
user_management_admin |
You can only access the User Management if profile user_management_admin has been assigned at least to one user. Therefore, every Scheer PAS installation is delivered with one standard user management admin. | PAS 21.1 | ||
Deprecated Profiles* | ||||
- | platform_admin |
| - | Deprecated as of PAS 21.1 |
- | rpa_admin |
| - | Deprecated as of PAS 21.1 |
* in use until version 20.1.8 |
User Profiles
The following list of user profiles can be searched: Use the available filter fields.
Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.
The table is being loaded. Please wait for a bit ...
Portal Tile | Profile | Description | Further Information | PAS Version |
---|---|---|---|---|
api_devportal_user |
| PAS 21.1 | ||
api_management_user |
| PAS 21.1 | ||
analytics_user |
BPaaS customers do not need the two additional profiles. But they can use the profile _dashboard_access_processes to grant an administrator access to all processes available in the system for use in Process Mining. | |||
bpaas_design_user bpaas_execution_user |
A BPaaS design user needs both profiles to be able to model and execute apps.
| |||
cron_manager |
| PAS 20.1 | ||
file_manager_user |
| PAS 21.1.2 | ||
integration_user |
We recommend using container deployment as the default deloyment target starting with PAS 23.1. For further information see:
| PAS 21.1 | ||
- | pas_base |
| PAS 20.1 | |
- | portal_base |
| PAS 22.1.1 | |
pas_user |
Users who should only be able to run Designer applications do not need the pas_user profile. They only need to be assigned the application profile. | PAS 20.1 | ||
process_monitor_user |
| PAS 21.1.2 | ||
xuml_monitor_user |
| PAS 21.1.4 | ||
Deprecated Profiles* | ||||
- | rpa_robot |
| - | Deprecated as of PAS 21.1 |
- | rpa_user |
| - | Deprecated as of PAS 21.1 |
* in use until version 20.1.8 |
- No labels