# Invitations should be compatible with SSO

**URL:** <https://meta.discourse.org/t/invitations-should-be-compatible-with-sso/20813>\
**Category:** Feature\
**Tags:** invites\
**Created:** [October 6, 2014, 1:12am UTC](https://meta.discourse.org/t/invitations-should-be-compatible-with-sso/20813 "2014-10-06T01:12:25Z")\
**Posts on this page:** 1\
**Showing post:** 23

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [April 28, 2016, 12:19am UTC](https://meta.discourse.org/t/invitations-should-be-compatible-with-sso/20813/23 "2016-04-28T00:19:08Z")

</div>

Sure I totally support adding that. Semantics are a bit tricky though … something like:

`groups:a,b,c`

The tricky thing semantically is how to “remove” users from the groups if you sync SSO?

Perhaps couple an optional setting of “sso\_allowed\_groups” that lists the groups that are “settable” via sso. Then when you specify groups we can also ensure you are not mistakenly in any other `sso_allowed_groups`

---

_[View the full topic](https://meta.discourse.org/t/invitations-should-be-compatible-with-sso/20813)._