Loopon supports Single Sign On (SSO) as an enterprise feature to hotel chains.
This will allow hotels to authenticate staff through their regular Identity provider (such as EntraId, Active Directory, Azure AD and many other common names) using the SAML2 standard.
It is a recommendation to use SSO to increase security within hotel chains.
Limiting access to employees that have left the chain
Staff that leaves the chain will no longer be able to log in to Loopon as soon as they are removed from the chain identity provider, which is a great improvement to security. Accounts created will still stay within Loopon and will need manual removal if needed.
Security policies
All policies such as 2FA, password complexity, password renewal rules etc. are handled by the authentication provider used by the chain and no longer through Loopon.
Provisioning new users
New users authenticated by the chain iDP will be added to Loopon automatically.
Set up process
The client and Loopon will set up a direct technical contact representing both organizations for exchanging configuration, doing set up and common tests.
Information provided:
| Information | Comment | Responsible |
| Link to Loopon Meta Data | Provided by Loopon, implemented by client |
|
| Identity Provider Meta Data | Loopon will use online access to XML definitions and certificates. | Provided by client, set up in Loopon by Loopon |
Information exchanged:
| Attribute | Comment |
| unique email address of user for use as ID | |
| firstName | First name of user |
| lastName | Last name of user |
| propertyCode | Unique identifier to which property user should be assigned |
| isSuperUser | Boolean, true if user should access property settings |