Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 8 Next »

Manually create users in Studio

Add new users in Studio by using the button "add new"

Remember that a Cobundu user needs to be linked to an IWMS user in order to have certain rights (eg to make a reservation or to book a ticket). So make sure the users exist in MCS first, this way you can link them during the upload.

 

UID (Unique ID within Studio) and sumorea e-mail address will be created using

  • (short) tenant
  • first name
  • last name

 

Login to Cobundu (Studio, Go, touchpoints) is possible via either

  • UID
  • sumorea e-mail address
  • e-mail address

 

Upload of multiple users at once (batch upload) is possible using the import-functionality. Check import_cobundu_users.xls as example:

  • all fields are mandatory (incl default password to start with)
  • document may not contain hyperlinks (so better to set e-mail address as text)

 

Automatic creation of Cobundu users

Initially designed as SSO (Single Sign-On) for Cobundu, the set-up of Cobundu SSO has the hidden advantage that for every (new) Cobundu user signing in, upon first login, Cobundu creates an account on-the-fly and the user can start using the system.

Prerequisites for Automatic creation of Cobundu users:

  • MCS account for user must exist
    • Ideally, an HR interface takes care of automatic creation of MCS users
    • In case the logged in user doesn’t exist in MCS, the user will not be able to use any MCS-dependant features like making reservations.
  • Cobundu SSO (receiving following attributes from the identity provider: "MCS login ID", "First Name", "Last Name" and "E-Mail“)
    • In case the “MCS login ID” attribute is not correctly mapped, the user will not be able to use any MCS-dependant features like making reservations.

 

A user logging in with Cobundu ID (tenant.ID) is recognized as being part of a tenant where SSO has been setup and Cobundu will automatically create a Cobundu account.

A user logging in with e-mail address is not yet supported (status 4/11/2020), but is foreseen to be implemented by latest Q1 of 2021. It uses a whitelist of e-mail providers (eg @spacewell.com or @mcs.be) to check the tenant.

 

More information on Cobundu SSO can be found in this presentation (keep in mind: Cobundu SSO only available for Go.cobundu.com and Personal Assistant)

 

Presentation in French:

 

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”).

 

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.

 

 

  • “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)

 

  • No labels