The following is generally applicable for add-on packs:
Add-ons have as a rule an own role concept.
- In the SE Manager, explicit permissions for individual add-ons are assigned by add-on-specific roles:
- A prerequisite for access to an add-on is an account with an add-on-specific role.
Thus, the account has access to all instances of the add-on in the SE administration area. - The role or authorization within the individual add-on results from the role defined for the account in the SE Manager.
- A prerequisite for access to an add-on is an account with an add-on-specific role.
The mapping of SEM roles with access to add-ons to the individual add-on internal roles or permissions is shown in the following table ("-" means no access; basic roles not shown do not have access to any add-on):
SEM Basic role openSM2 openUTM ROBAR STORMAN Administrator
Administration
Master + Administration Write
Administrator
Administrator
Service
Administration
Master + Administration Write
Administrator
Administrator
OPENSM2 administrator
Administration
-
-
-
OPENSM2 information
Monitoring
-
-
-
OPENUTM administrator
-
Master + Administration Write
-
-
OPENUTM operator
-
Administration Write
-
-
OPENUTM information
-
Administration Read
-
-
ROBAR administrator
-
-
Administrator
-
ROBAR operator
-
-
Operator
-
STORMAN administrator
-
-
-
Administrator
STORMAN information
-
-
-
Storage info