Access is checked, not assumed
Live guild and role verification connects Discord identity to permission-scoped ticket access. Member conversations and internal staff notes are kept distinct.
PROJECT 01 / COMMUNITY INFRASTRUCTURE
Support with structure. Access with boundaries.
A community support platform connecting Discord identity with structured conversations, staff workflows, and accountable decision-making.
Identity & access · Workflow engineering · Evidence & audit trails
Next.js · TypeScript · Discord OAuth · Prisma · SQLite
01 / THE CHALLENGE
Community support crosses several boundaries: who is asking for help, which staff can see a ticket, and what needs to stay private. Keeping those boundaries clear matters as much as making the queue easy to use.
Discord provides identity and live role verification. Ticket conversations, staff notes, evidence, assignment, and auditing remain in the web application. That separation gives each part of the system a clear responsibility.
02 / ENGINEERING DECISIONS
Live guild and role verification connects Discord identity to permission-scoped ticket access. Member conversations and internal staff notes are kept distinct.
Evidence handling, assignment, and audited message editing give staff a traceable record. Incident management groups related tickets without exposing internal incident summaries to members.
Saved replies, reply drafts, ticket search, watcher lists, and an in-app notification inbox support the repetitive work around each conversation.
03 / WHAT IT BRINGS TOGETHER
THE THREAD THAT RUNS THROUGH IT
This project brings software engineering and security concerns into the same workflow: identity, permissions, data handling, and a usable interface all need to agree.
Discuss this project ↗