Documentation
Getting started

Set up Knytly in five steps.

From zero to a working Discord bot with tickets and staff permissions — in under ten minutes.

01

Sign in with Discord

Go to knytly.com and click Sign in. Knytly uses Discord OAuth — no separate account or password required. You will be redirected back to your dashboard after authorizing.

Screenshot coming soon
  • You must be the server owner or have administrator permissions on the target server.
  • Knytly only requests the Discord permissions it actually needs — no message read access.
02

Invite the Knytly bot

After signing in, the onboarding wizard will guide you to add a server. Select your server from the list and click Invite bot. Discord will show a permission dialog — accept it to install the bot.

Screenshot coming soon
  • The bot needs Manage Roles, Manage Channels, and Send Messages permissions to operate correctly.
  • You can also invite the bot later from Settings → Bot in your workspace.
03

Configure your first module

Pick the module most relevant to your community. Tickets is a good first choice for most servers — create a category, configure the staff role, and create your first panel. The bot will post a button in your chosen channel.

Screenshot coming soon
  • All modules are disabled by default and must be enabled individually in their Settings tab.
  • Changes save instantly for toggles. Forms require an explicit Save.
04

Add your staff

Go to Staff Panel → Groups and create your first group. Assign a Discord role to the group, then select which permissions that group holds — for example, tickets.claim and tickets.close. Staff with the assigned role will have those permissions automatically.

Screenshot coming soon
  • Free plan allows up to 2 staff groups. Pro allows 10, Pro+ is unlimited.
  • Permissions are additive — a staff member with multiple roles inherits the union of all permissions.
05

Go live

Double-check your module settings, confirm the bot is online (green dot in Settings → Bot), and announce the new system to your community. You can monitor activity in the Audit Log and refine settings at any time without downtime.

Screenshot coming soon
  • Consider sending a message to your server explaining the new ticket panel or welcome flow.
  • Enable Logging early to get a full audit trail from day one.