SCIM for Skedda: Secure Access, Automatic Provisioning

Automate User Provisioning with SCIM for Skedda

IT shouldn’t have to maintain multiple sources of truth.

That’s why Skedda now connects directly to Microsoft Entra ID via SCIM integration – this means no more manual provisioning, and no more repeated updates to profiles across systems. 

All of this makes it easy to roll Skedda out at your organization. User information like names, emails, department, and language preferences all flow seamlessly into Skedda from your employee directory and continue to stay in sync as people join, move, or leave. 

For IT, this means one source of truth and stronger security; for HR, faster onboarding with accurate, up-to-date data. The result is a system that mirrors reality, without spreadsheet workarounds.

SCIM: User Management, Without the Work

Rolling out new software for your organization can be a daunting task. Whether you’re seeking buy-in from stakeholders or just trying to make the admin work easier, here’s how SCIM-based provisioning makes implementing Skedda a quick and painless process. 

1. Ensures Secure Access

Identity belongs in one place: your organization’s directory. With SCIM enabled, Skedda treats your identity provider as the single source of truth. When someone joins, moves teams, or leaves, access updates flow automatically. If a user is removed in Entra ID, they’re instantly deactivated in Skedda and their historical bookings are anonymized to the default “Casual user,” which avoids dangling accounts and messy cleanup.

Security isn’t just about on/off. It’s also about scope. Each Skedda venue has its own SCIM base URL, which aligns with how SSO is configured and lets you grant or limit access at the venue level. That’s especially helpful for multi‑location organizations that want tight separation between sites without extra admin work.

Why it matters for rollout: fewer manual steps for IT, less room for unauthorized access to company resources, and more peace of mind for future changes in headcount.

2. Saves Onboarding Time

You hire someone new and add them to your employee directory, and… that’s it. 

Their Skedda profile is created automatically with key attributes like name, work email, and active status, so there’s no double‑entry and no waiting on invites. Admins can immediately book a desk for a new hire on their first day instead of waiting for them to log in via SSO and attempt to do it themselves. The result? A smoother first day, a better first impression, and faster end-user adoption. 

Here’s where it gets even better: space access! Groups in your IdP map directly to user tags in Skedda. If you already use custom booking rules based on user tags, SCIM brings those tags across automatically. That means when someone joins Engineering in your directory, they can book the right labs or floors in Skedda immediately, no manual tag wrangling required. Skedda can even create new user tags based on incoming SCIM groups to keep things tidy.

Why it matters for rollout: day‑one space access compliant with your policies, fewer help‑desk tickets, and no spreadsheets to manage.

3. Keeps Everything in Sync

People change roles, teams restructure, emails get updated. With SCIM, Skedda stays aligned with your employee directory as those updates happen. Core attributes like name, work email, language preferences, and groups can be synced automatically, which prevents profile drift across systems and keeps permissions consistent over time.

Skedda implements the core SCIM 2.0 resources for Users and Groups, using Groups to drive user tags and policy in Skedda. As team members change departments, receive new certification, or gain promotion, their associated user tags and access to space in accordance with your policies will remain up to date – without the administrative overhead. 

Why it matters for rollout: your employee directory stays the single source of truth, and Skedda simply reflects it. That means less maintenance for admins and fewer surprises for end users.

How to Set Up SCIM with Microsoft Entra ID

Ready to get started with SCIM in your Skedda account? Check out our detailed help guide here. For now, here are the basics:  

1. Create a custom SCIM app in Entra ID
   Add a new non‑gallery enterprise app and give it a clear name for your venue.
   
   
2. Assign users and groups
   Decide whether to provision all users or a pilot group. Assign them to your new app for a controlled rollout.
   
   
3. Enable SCIM in Skedda
   Go to Settings → SSO / SAML 2.0 and enable SCIM, then copy the SCIM Base URL and Token.
   
   
4. Configure provisioning in Entra ID
   Paste the Base URL and Token into the Entra ID Provisioning tab. Test the connection, then start provisioning.
   
   
5. Map attributes and groups you want to provision
   ‍For more details about doing this correctly, view our full help guide.
   

See SCIM in Action

Curious how SCIM looks in your environment? Request a demo today to see how easy it is to transfer existing user data into Skedda.