BotFrame

Access workflow guide

How to make a Discord verification bot

Create an explicit member interaction that checks current access, assigns a verified role, and confirms the result without hiding the permission path.

Define what verification proves

A button click can confirm that a Discord member saw and used the verification component. It does not by itself establish real-world identity, age, payment, or ownership of an external account. Match the permissions granted to the assurance the workflow actually provides.

Build the workflow

  1. Publish the verification componentCreate a clear button or select option in a channel unverified members can access.
  2. Add the interaction triggerMatch the stable Custom ID so unrelated components cannot enter this workflow.
  3. Check the member's current roleRoute existing verified members away from a redundant assignment.
  4. Add the verified roleChoose the role deliberately and confirm the bot can manage it.
  5. Confirm and test both branchesTell the member what changed, then test verified and unverified states before publishing.

Keep the role narrow

Do not use public verification to grant administrator or staff permissions. Review every channel permission inherited by the verified role and keep the bot token protected during setup.

Review the complete workflow

Use the verification bot template with the component interaction trigger and Add role node.