- 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)
- 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.


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.
- appear in the organization members list,
- retain repository access, and
- remain active if she has an open session from earlier.

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.
- 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.

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?”

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.
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).
- GitHub Docs — SCIM and SAML: https://docs.github.com/
- GitHub Docs — Team Sync and provisioning: https://docs.github.com/
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).