Faster/configurable Team Sync (or SCIM-based team membership) for standard SAML SSO enterprises

[IraFischler]

🏷️ Discussion Type

Product Feedback

Body

Team Sync currently reconciles IdP group → GitHub team membership on an hourly-minimum cadence with no configurable interval (per "Synchronizing a team with an identity provider group"). True SCIM-based, near-real-time team provisioning is only available to Enterprise Managed Users — existing standard enterprises can't convert to EMU without a full re-platform of every org, repo, and user identity.

This makes Team Sync unusable as the access-control layer for just-in-time/on-demand elevation. We use a JIT tool (Apono) to grant temporary GitHub admin access via an Okta group, and measured the (via the Teams API) :

Grant (Okta group updated → user appears in GitHub team): ~24 min
Revoke (Okta group updated → user removed from GitHub team): ~69 min
Both fall inside GitHub's documented "at least once every hour" behavior, so this isn't a bug — it's a structural limitation for anyone trying to use Team Sync as a real-time access control mechanism. A ~20-70 minute grant/revoke lag is either too slow for incident response, or leaves elevated access live long after it should be revoked — a real gap for time-bound access controls (SOC2, least-privilege).

Ask: extend real-time/SCIM-based team membership provisioning to standard SAML SSO enterprises (not just EMU), or make the Team Sync interval configurable for orgs that need faster reconciliation.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[queenofcorgis]

Hi @tvoyagetrends-max , thanks for participating!

Unfortunately, we don’t currently have moderators for languages other than English. Until that changes, we need to ask that everyone use English here in the GitHub Community when posting to ensure discussions are adhering to our Code of Conduct.

We’ll be hiding your comment for now, but please feel encouraged to create a new reply in English if you still want to participate.