Spoke
Community
The public server. Members stay here. Staff traffic leaves for the Hub.
Discord staff bot
Keep the community loud.Keep the staff room quiet.
Synapse sits between them. A public server can stay public. Staff work can happen somewhere private. One server can do both.
Bot status Checking
Hub
Staff
The private server. Triage lands here, and staff decisions go back to the Spoke.
Standalone
One server is enough.
The same bot, both jobs. The triage channel stays hidden from everyone else.
Link code
K4N8QP
A Hub mints a real 6-character code in /setup. Rotating it leaves current Spokes connected. This one is just for show.
How it starts
Step 1
/setup
Initialize a Hub and choose the triage channel.
Step 2
Link a Spoke
The Spoke enters the link code. The Hub approves the request.
Step 3
/settings
Place the ticket panel and tune logs, ranks, and alerts.
On the staff side
Ranks
A rank is a named position tied to a Discord role, with its own level. A lower level cannot act on a higher one.
Hire and fire
Hiring opens a staff profile, gives the rank, and grants the primary staff role. Firing takes them back.
Leave
Hired staff request leave with a reason and dates. Someone with leave approval can approve, deny, or end it.
Tickets
Members open a private thread from a panel. A linked Hub gets a matching triage thread, and messages typed on either side are mirrored. Claim, notes, close, and transcripts stay with staff.
Strikes
Ranks that can issue strikes can view a hired member’s record, add a strike with a reason, or remove an active one. The change posts to the discipline log.
Logs and settings
Per-kind log channels, ranks, the ticket panel, auto-close, and an alert role all live in /settings.
What it hears
/setup
/staff hire
/loa request
/ticket claim
/ticket summary
Setup, staff, leave, and settings stay on slash commands, buttons, and forms. Message content is read only inside open ticket threads so those conversations can be mirrored. Other channels stay unread.