Skip to main content
This guide clarifies three frequently confused identity concepts for GitHub Enterprise administrators and exam candidates: SAML, SCIM, and Team Sync. Understanding the difference is essential for secure, automated identity lifecycle management and for avoiding common operational gaps that cause security incidents.
  • SAML = authentication (who are you when you try to log in)
  • SCIM = provisioning/deprovisioning (create or remove accounts and org membership)
  • Team Sync = mapping IdP groups to specific GitHub teams (assign entitlements)
A short hotel analogy makes the distinction stick. Imagine a large hotel:
  • SAML is the front-desk clerk who checks your ID at arrival (confirms identity for login).
  • SCIM is the automated hotel management system that issues a room key at check-in and automatically deactivates it at checkout.
  • Team Sync is the loyalty-tier placement that decides which floor/room category you belong to.
A slide titled "SCIM Is the Automated Key System" illustrating a hotel's automated management system that issues a room key at check-in and automatically deactivates it at checkout. The graphic shows a room card labeled "room 412" and a crossed-out card to indicate the key becomes inactive.
For a 2,000-room enterprise hotel, manual processes don’t scale. Without SCIM, thousands of “ghost” keycards remain valid — physically held by former guests who checked out months ago.
A presentation slide titled "Ghost Keycards at Scale" showing "2,000 rooms in one enterprise hotel" with many illustrated physical keycards labeled "Without SCIM." It highlights that these cards can remain physically valid (held by guests who checked out) and notes "Automation is the only thing that scales."

SAML (Authentication / Single Sign-On)

SAML (Security Assertion Markup Language) provides single sign-on and identity assertions at login time. It answers the question: “Can this person authenticate right now via the IdP?” SAML does not manage ongoing organization membership or perform deprovisioning.

The operational gap SAML leaves open

SAML prevents authentication once the IdP account is disabled, but it does not actively remove that user’s organization memberships or team access within GitHub. That creates a gap between authentication and authorization state inside GitHub.
The image is a slide titled "The Gap SAML Leaves Open" showing two cards: on the left "Can they log in? Handled by SAML" and on the right "Are they still a member? Nobody is watching," with the word "gap" between them. It illustrates an operational gap between authentication and ongoing membership verification.
Consider a real example: When Jane’s Okta account is disabled because she resigned, SAML blocks further single sign-on attempts, but she may still:
  • appear in the organization members list,
  • retain repository access, and
  • remain active if she has an open session from earlier.
A presentation slide showing a team members list for "acme-engineering" with "jane-d" marked as having left the company. Beside it are three points noting she’s still in the members list, still has her repositories, and still has an active session open.

SCIM (Provisioning / Deprovisioning)

SCIM (System for Cross-Domain Identity Management) closes the membership gap. It allows your identity provider to call GitHub’s SCIM REST API to create, update, or remove organization users and attributes automatically when identity lifecycle events occur.
A slide titled "SCIM Closes the Gap" showing a UI panel labeled "People in acme-engineering" with user entries (priya-r, marcus-l, jane-d flagged as "removing", and tomas-k). A purple rounded button above reads "SCIM actively removes her."
From a technical perspective:
  • GitHub exposes a SCIM REST API endpoint that your IdP calls on provisioning events.
  • Authentication to that endpoint uses a GitHub-generated bearer token (not SAML certificates).
  • Treat the SCIM token as a highly privileged secret — anyone with it can programmatically add or remove organization members.
Example HTTP usage:
Rotate the token periodically and store it securely. Do not embed it in client-side code or public repositories.
A presentation slide titled "Treat the Token as a Secret" showing two rounded tip cards: "Rotate it periodically" and "Treat it as highly privileged" each with an icon. A small "© Copyright KodeKloud" appears in the corner.
For official configuration steps and supported identity providers, see GitHub’s SCIM documentation: https://docs.github.com/en/enterprise-cloud@latest/admin/authentication/configuring-identity-provider-for-saml-and-scim

Team Sync (Group-to-Team Mapping)

Team Sync maps IdP groups to GitHub teams. It answers a different question than SCIM:
  • SCIM: “Is this person allowed in the organization at all?”
  • Team Sync: “Which team(s) in the organization should this person belong to?”
Use Team Sync to automatically assign team membership based on IdP group membership—useful for permissions and role-based access control.
A presentation slide titled "Team Sync Goes One Level Deeper" contrasting SCIM's question ("Allowed in the organization at all?") with Team Sync's question ("Which specific team are they on?"). On the right is an "acme-engineering" team list showing platform, payments (highlighted), and mobile.
Team Sync depends on provider and GitHub product support—verify compatibility in the GitHub docs.

Best Practice: Run Both SCIM and Team Sync

For a fully automated, secure identity lifecycle, run SCIM for provisioning/deprovisioning and Team Sync for team-level entitlements. SCIM ensures no stale accounts remain; Team Sync ensures correct team assignments.
A slide titled "Run Both, Not One" showing two colored boxes—"SCIM in the organization?" and "Team Sync on which team?"—with arrows merging into the phrase "A fully automated identity lifecycle." The graphic conveys running both systems together to achieve automated identity management.

Quick Reference Table

Exam-focused summary

  • If the question asks which system automatically removes a GitHub organization member when the identity provider account is deprovisioned, the answer is SCIM.
  • SAML handles authentication (single sign-on) and does not remove org membership.
  • SCIM performs provisioning and deprovisioning via authenticated API calls using a bearer token.
  • Team Sync maps IdP groups to GitHub teams and controls team membership (check provider support and GitHub docs).
Useful references:
Exam tip: Remember the hotel analogy — SAML is the front desk (login), SCIM is the automated key system (provision/deprovision), and Team Sync is the loyalty-tier assignment (team membership).

Watch Video