When someone leaves your organization, you can remove them from your venue and decide what should happen to their bookings - all in one step. You can also set a default policy so that users removed automatically through directory sync (SCIM) are handled the same way every time.
This article covers how user removal works, the options available to you, and how bookings are handled across Skedda-only venues, connected calendars, and two-way sync.
How it works
When you remove a user, you choose what happens to their future bookings: keep them (anonymized) or permanently delete them.
Past bookings are always kept and anonymized, so your historical data and analytics (occupancy, utilization) stay intact.
You can remove a user even if they have two-way sync bookings - there's no need to clean up their bookings in Google or Microsoft first.
Removal is processed in the background, so the user disappears from your list right away while their bookings are handled.
Past vs. future bookings
Regardless of which option you choose:
Past bookings are always retained and anonymized - reassigned to the "Casual user" so they keep their time, space, and notes but no longer carry the person's identity.
Future bookings are the ones you decide about when removing the user.
Removing a user manually
Go to your Users list.
Open the menu for the user you want to remove (the downward arrow on the right of their row).
Choose to remove the user. A Remove user confirmation dialog appears.
The dialog confirms: "This action will delete [user] from the system. Past bookings will be anonymized. Decide what happens to their future bookings:" - then pick one of the two options below.
Click Remove User to confirm.
The user is removed from your list immediately. Their bookings are then processed in the background, so it may take a short while for all changes to appear - especially where a connected calendar is involved.
Your two options for future bookings
Keep bookings (anonymized)
Future bookings stay on the schedule but are no longer tied to the removed user. Choose this when you want to preserve the booking history and analytics.
Permanently delete bookings
Future bookings owned by the user are permanently removed from Skedda. Use this when those bookings are no longer relevant and you want to free up the spaces and reduce clutter. Past bookings are still kept and anonymized.
Bookings in connected calendars (one-way and two-way sync)
If you have resources synced with an external calendar (Google Workspace or Microsoft), the wording in the dialog adapts to your provider, and the behavior differs slightly:
Keep bookings (anonymized): Future bookings remain in Skedda and stay anonymized. The link to the external calendar event is preserved.
Permanently delete bookings in Skedda and [provider]: Future bookings are deleted in Skedda. Because Skedda can't delete events in Google or Microsoft directly, the corresponding events are declined in the connected calendar instead.
Note: You might have resources synced with your external calendar. It may take several hours for booking updates to be reflected in your connected calendar.
Automatic removal via SCIM (directory sync)
If your venue uses SCIM to provision and deprovision users automatically from your identity provider (for example Okta or Microsoft Entra ID / Azure AD), you can set a single default policy that applies to every user removed this way. Admins don't choose per-user behavior in real time for SCIM removals - the pre-set policy is applied automatically.
To configure it:
Go to Settings and open your SCIM Settings.
Under the user offboarding section you'll see: "When a user is deprovisioned, their past bookings are anonymized. Their future bookings are:"
Choose your default policy:
Kept and reassigned to Casual user (or Kept and anonymized when an external calendar is connected)
Permanently deleted (or Permanently deleted in Skedda and [provider] when an external calendar is connected)
This setting takes effect at scale and is intended as a standing policy rather than something you change for each individual user.
Important notes
Past bookings are never deleted - they're always retained and anonymized for data integrity, transparency, and analytics.
Removal is processed in the background. The user disappears from your Users list immediately, but booking updates (especially in connected calendars) can take several hours to fully complete.
For two-way sync, bookings are declined in the external calendar rather than deleted, because Skedda can't delete events in Google or Microsoft on the user's behalf.
Two-way sync bookings no longer block user removal.