Gating Access
Overview
Gating access is a Discord permission pattern. Nox helps by assigning and removing roles through Greetings and Role Boards, while Discord channel permissions decide which channels those roles can see or use.
Common patterns
Welcome-first access
Give new members a starter role when they join, then point them at rules, introductions, or a verification channel with a greeting message.
Role-board access
Let members choose topic, notification, event, or private-area roles from a managed board after they have reached the right onboarding step.
Layered handoff
Use Greetings for the first gate, then Role Boards for optional or interest-based access once a member has the baseline role.
Temporary spaces
Use temporary Role Board grants for events, workshops, launches, or private rooms that should expire without staff cleanup.
Setup checklist
Decide the Discord roles that represent each gate, such as new member, verified, event access, or topic opt-in.
Configure Discord channel permissions first. Nox changes roles; Discord decides what those roles can see, read, send, or join.
Configure Greetings if new members should receive a message, starter role, delayed role, or second welcome when a trigger role is added.
Configure Role Boards when members should self-select roles, pass option eligibility rules, or receive temporary access.
Test with a non-admin account so administrator permissions do not hide a broken channel or role setup.
Suggested flow
Create the access roles
Create the roles in Discord and place Nox above every role it needs to add or remove.
Lock the channels
Set channel permissions around the access roles. Keep rules, help, and staff-contact channels reachable so members are not stranded.
Add the welcome handoff
Use Greetings to explain the next step, assign the first role, or respond when a verification role is granted.
Publish role choices
Use Role Boards for optional access roles, required-role gates, denied-role checks, minimum member age, or temporary role grants.
Important notes
Nox must have Manage Roles and must sit above every role it should add or remove. Discord role hierarchy failures block the role change.
Greetings can assign a first role, schedule a delayed first role, send a welcome message, and run a second welcome when a trigger role is newly added.
Role Boards can gate individual options with required roles, denied roles, and minimum member age before applying configured role changes.
Role Boards keep their board message updated. Greetings welcome messages are not tracked after they are sent.
Channel access should always be tested in Discord. If the role change works but the channel is still hidden, the issue is usually channel overwrites.
Troubleshooting
A member did not receive the access role
Check Manage Roles, role hierarchy, the configured greeting or board option, and whether the member matched the trigger or eligibility rules.
A channel is still visible after removing a role
Review Discord channel overwrites for other roles the member still has. Nox may have removed the configured role correctly while another role still grants access.
The board works for admins but not members
Test with a normal account. Admin accounts bypass many channel restrictions and can make a broken gate look healthy.
