Table of Contents

Manually create users in Studio

...

Roles & Profiles

Roles and Profiles for each tenant can be found/ are described on Studio (scroll to the bottom of the tenant: under Users, you'll find “Roles & Profiles”).

Image Added

Depending on the needs per customer, other roles can be added to the tenant (select "Add New"); eg Work Assistant roles that can access different Workorder overviews.

Image Added

• “No roles found, unprivileged user”: user can access End-user Cobundu touchpoints (GO + PA)
• “Admin” role is needed to access Studio, DeviceControl
• "Developer" role is assigned typically to users who have the rights to view/consume/integrate COBUNDU APIs with touchpoints. As these users can also be external developers who work on integrating COBUNDU with their systems, such users should not have access to COBUNDU touchpoints. On GO, users with only developer role are automatically redirected to the API documentation upon login and cannot use any other front-end features.On Personal Assistant, an alert will be shown and the user will not be allowed to continue.
• “WorkAssistant” role is needed to give access to specific overviews with workorders, see configuration instructions on https://confluence.mcs.be/display/SUM/Work+assistant

Roles and Profiles for each tenant can be found/ are described on Studio (scroll to the bottom of the tenant: under Users, you see “Roles & Profiles”).

New ones can also be added there (depending on the needs for this customer, other roles could be added to the tenant; eg Work Assistant has been added to MSO but not other tenants that did not show an interest in using Work Assistant)