Guide
Guide
Your directory creates, updates and disables SpotBooker accounts itself: someone who leaves loses access the same day.
Microsoft or SAML sign-in only acts when someone signs in. With SCIM, your directory (Microsoft Entra ID, Okta or any SCIM 2.0 tool) tells SpotBooker about every arrival, change or departure. Provisioning is included in the subscription and available during the free trial. Only your workspace administrators can set it up.
Click “Generate a token” and copy it straight away: it is shown only once, SpotBooker keeps only a fingerprint of it. Afterwards, only its creation and last-used dates remain visible. Lost the token? Generate a new one: the old one stops working at once. “Revoke” cuts the directory's access.
It ends with /scim/v2: https://spot-booker.app/scim/v2. Your directory asks for it as “Tenant URL” or “Base URL”.
In your directory, open the SpotBooker application (the sign-in one, if you have it) and turn on automatic provisioning. Paste the URL and the token, using bearer token authentication (“Bearer token” or “Secret token”), then test the connection. In Microsoft Entra ID, this is the Provisioning section of the enterprise application; elsewhere, menu names vary. Finally, assign the people and groups to sync.
SpotBooker reads the identifier (userName, often the sign-in address), the primary email address, first name, last name and active status. Without an email address, userName is used if it looks like one. Your directory's default mappings usually fit.
Accounts arrive in the user list as members, with no admin rights. Someone who already had an account in your workspace at the same address is taken over, not duplicated. The token's last-used date confirms that your directory has connected.
Groups sent by your directory appear with their member count. Link each one to a SpotBooker group: its members join it right away, then join and leave it as the directory changes. An unlinked group is received but changes no rights, and a group managed by hand in SpotBooker is never touched.
As soon as your directory disables or removes the person, they can no longer sign in by any means, and their open session closes. Nothing is deleted: their bookings stay in place.
If they had upcoming bookings (confirmed or pending, not yet started), administrators see on their dashboard “Mary Martin has left the directory: 3 upcoming bookings”. “Cancel all” cancels these bookings and frees the resources; the booker and their guests are notified by email, as for a cancellation from the schedule. “Keep” leaves them in place, for instance when a colleague takes over the slots. The decision is recorded and the alert disappears.
If the person comes back into the directory, their account is reactivated automatically and any alert still open closes. The account cannot be reactivated by hand in SpotBooker: the directory stays the reference.
| What you see | What to do |
|---|---|
| The connection test fails (error 401) | The token is wrong, revoked or replaced by a newer one. Generate a new one and paste it as is. Also check that the URL ends with /scim/v2. |
| Every request gets a 403 error | The free trial ended without a subscription. The token and settings are kept: sync resumes as soon as you subscribe. |
| Someone is not created (conflict, error 409) | Their address is already used by an account in another SpotBooker workspace, or their identifier by another account in yours. Write to us if the person should join your workspace. |
| Disabling an administrator is refused (error 400) | They are the last active administrator of your workspace. Appoint another one in SpotBooker, then run the sync again. |
| No group appears | Your directory has not sent any yet: assign the groups to the application and check that group sync is on. They appear after the next cycle. |
| No alert after a departure | The person had no upcoming bookings: their account is disabled and there is nothing else to decide. A booking that has already started does not count. |