Inviting Kharat & permissions
How to invite Kharat to your server, which Discord permissions each module relies on, and who can use the dashboard.
Inviting the bot#
The fastest way to invite Kharat is the Invite Kharat button on the home page. It builds an invite link with the permissions the bot needs.
You can also invite from the dashboard: after signing in, servers the bot is not in yet show an invite page instead of a dashboard. Inviting requires the Manage Server permission on the target server — Discord enforces this on its own invite flow.
Permissions the modules rely on#
Kharat does not gate features by checking its own permissions first — commands run and missing permissions surface as Discord API errors. Granting the set below up front avoids that:
| Permission | Used by |
|---|---|
| View Channels, Send Messages, Embed Links | Every module: replies, embeds, panels |
| Read Message History | Snipe recovery, ticket transcripts |
| Add Reactions | Snipe and reaction tooling |
| Attach Files | Ticket transcripts and file features |
| Moderate Members | ,timeout, ,unmute, anti-spam timeouts |
| Ban Members / Kick Members | ,ban / ,kick |
| Manage Roles | Gulag role assignment, activity role updates |
| Manage Channels | Server Stats channel renames, ticket category handling |
| Manage Messages | Anti-invite deletion, pin/unpin flows |
| Manage Threads | Thread-based features |
Who can use the dashboard#
Dashboard access is decided by Discord itself. After signing in with Discord OAuth, the server list is filtered to guilds where you are:
- the server owner, or
- a member with the Administrator permission (bit 3).
No other permission (not even Manage Server) grants dashboard access, and there is no separate invitation system. See Account & access for session details.
After the invite#
Once the bot is in the server, head to First steps to enable modules and confirm everything works.