...
On GO and Studio, if your customer has SSO installed and you want to bypass (and login using your Cobundu ID), go to https://go.cobundu.com/no-sso or https://studio.cobundu.com/no-sso; select "Log in with your Cobundu credentials"; then log in with your Cobundu ID and password.
Role Mapping (see Roles & Profiles
...
)
Initially, SSO was creating users, but that's as far as the user management went. There is no update done, no deletion or deactivation. If a user is set to disabled in the IWMS, the consequence will be that the Cobundu user is still active, but does not have any IWMS rights anymore: the user can login to Cobundu touchpoints and browse reservable rooms, floorplans etc, but as soon as they want to make a reservation or book a ticket, this will not be possible (because they don't have the correct IWMSrights anymore).
...
View file | ||||
---|---|---|---|---|
|
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”).
...
...
! With great power comes great responsibility: make sure the Admin-user is aware of the Studio basics. Having access to Studio = having access to the Settings page + Sensor Devices mapping + Floorplan config + ... => a basic training in Studio is needed before access can be given.
- "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 Workplace App, an alert will be shown and the user will not be allowed to continue.
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.
- “Cleaning/WorkAssistant” role is needed to give access to specific overviews with workorders, see configuration instructions on https://confluence.mcs.be/display/SUM/Work+assistant
- Access to dashboards on GO can be restricted per role (under tenant > General settings > Dashboards)