Edit history

There is no native way to require new members to read and accept a community's rules before they get access. Operators who want this build it by hand with reaction-roles plus per-channel permission overwrites: hide channels from everyone, grant a "Member" role when someone reacts on a rules message, and hope nobody gets locked out. It is fragile, easy to misconfigure, inconsistent between communities, and keeps no record that a member actually accepted the rules. There is also no rules/welcome screen on join.

A native rules-acceptance gate (membership screening) at the community level:

• Owners/admins define the rules and enable the gate.
• On joining, a new member sees the rules and must explicitly accept them before getting access to channels (limited/read-only until then).
• Acceptance is recorded per member (who, when, which rules version).
• Optional re-prompt when the rules change.
• Configurable in community settings, with API + admin support so it works on self-hosted instances and can be managed by operators/bots.

Ideally this pairs with the onboarding guide in #1337 (rules gate first, then guided role/channel selection) for a complete join flow, with no custom bots or manual permission gymnastics.

Accept-rules-then-onboard is one of the first things community owners look for. Today self-hosters rebuild a worse version by hand, with a real risk of locking members out of their own community. A native flow would cut moderation/support load and make the new-member experience consistent. Complements #1337. Mockups can be added if useful.