...
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. The user can proceed to login.
A user logging in with e-mail address is now also supported: It uses a whitelist of e-mail providers (eg @spacewell.com or @mcs.be) to check the tenant. To whitelist an e-mail domain, add it to Settings > SAML SSO > "Allowed email domains (comma separated)" (underneath "Auto-Create user").
On GO, 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; select "Log in with your Cobundu credentials"; then log in with your Cobundu ID and password.
Keep into account that a side effect from SSO is also creating users, but that's as far as the user management goes. There is no update done, no deletion or deactivation. If a user is set to disabled in MCS, the consequence will be that the Cobundu user is still active, but does not have any MCS 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 MCS rights anymore).
More information on Cobundu SSO can be found in this presentation (keep in mind: Cobundu SSO only available for Go and Personal Assistant)
...