The following guide is for end users and head office users. For IT Administrators setup guide click here.
- Logging in
- Logging Out
- Managing users
SSO login is supported on iOS and Android in version 4.3.0 and up.
- On the login screen users will see an option to sign in with SSO.
- Once they select this, they are asked for the SSO key. This should be provided by your IT administrator who setup the SSO integration. This only has to be entered once and will be saved on the device for future login's.
- Once pressing Login, the user will be directed to your SSO login screen to sign in using your corporate credentials.
- You then enter your company credentials and if the account is linked to a store you are logged straight in.
Logging in on a desktop is very similar to logging in on mobile with SSO. In addition to the usual username and password, you can now choose to login with SSO:
Click Sign in with Single Sign On (SSO), then enter your SSO key and press login. Your SSO key is the one provided to you by your organisation. It may be your company name. Please check with your management to confirm this.:
You will then be taken to your corporate login page and be signed into the app.
Note: If you are using the same computer then we remember your SSO key so you don't need to keep re-typing it each time for a quick seamless login process.
If the user logs in and sees a 'Pending account' message, then this means the user hasn't been linked to a venue. This is due to their user either not having a store id, or an unknown store ID was passed. See 'Managing users' for more info.
To log out of the desktop or mobile apps you follow the usual logout process. This will clear your Qudini session and you will be logged out. Note that depending on the configuration of your SSO settings, you may not be logged out of your corporate login. If you are no longer using a device then we recommend you logout of your corporate session too. Speak to your IT teams to confirm how this works.
If you are already signed into your corporate credentials the next time you press login, you may not need to re-enter your password. This is expected.
Assigning roles to a 'Pending user'
If a user logs in without a matching store ID. Or the user is a venue admin user then they are first placed into a 'pending' state. This requires an admin to connect the user to the relevant store or venue admin permissions.
Within the Authentication settings there is a section called 'Manage SSO Users'. Here you can see a list of the pending users. Find the user you are looking for and press 'Connect'
The user details are displayed with an option to choose the venue this user should be allocated to or set them as a merchant admin.
Merchant admin: To give this user merchant level access (head office) then enable the 'Merchant admin' toggle. This will enable the user to login and will give them Merchant Admin access by default. If you wish to make them a restricted admin user then follow the guide here: Adding other merchant admin users
Venue user: To give the user access to only a specific venue, select the venue you want and press Connect. This will add them as a concierge and server to all queues by default. If you need to allocate admin access you can do this via the venue admin settings.
When a user is removed or archived in your user directory, they will no longer be able to login to Qudini.
We do not however automatically remove that user from our system. Users will need to be manually archived from the venue settings by an admin.