You make it sound so easy! ![]()
Our concern is that sites can be set up in many different ways and then expect the invite system to work in different ways as well. Security is a very real concern. So we will be treading carefully when making any more changes to the invite system.
My personal feeling is that the following approach would be best, because it doesn’t depend on an admin setting and makes the behavior crystal clear directly on the invite modal. It would be hard for even someone completely new to discourse to accidentally create and share an invite link that does something they do not expect. What do you all think?
- When
must approve usersadmin setting enabled - Toggle is shown to staff on the invite modal to create an invite that bypasses approval requirement. e.g.
[ ] Do not require approval by staff - Invites redeemed when toggle in (2) is selected let the user into the site without requiring approval
The assumption is that only staff should have access to this toggle, because the intent of the must approve users setting is to give staff control over who is allowed to join the community.
If there is sufficient demand for it, we could later consider adding an admin setting to determine who has access to this feature by group.