Vanta Documentation
Vanta knowledge base

Documentation

Install, configure, and troubleshoot Vanta with practical, step-by-step guidance.

01

Getting Started

Add Vanta to a Discord server and complete the first configuration steps.

  1. Click Add to Discord.Use the official Vanta authorization link.
  2. Select the Discord server.Choose the server where Vanta should be installed.
  3. Review requested permissions.Understand the access Vanta is requesting before continuing.
  4. Authorize Vanta.Complete Discord's authorization and verification flow.
  5. Return to your server.Confirm Vanta appears in the member list.
  6. Run the setup command.Begin configuring supported systems.
    /setup

Where supported, users may also use:

/autosetup

You need permission to add applications or bots to the Discord server. Setup commands may also require Server Owner or Administrator access.

Add to Discord
02

Inviting Vanta

Use only the official invite and verify the destination server before authorizing.

The official Vanta invite includes the bot and applications.commands scopes. The latter registers Vanta's slash commands with Discord.

Select a server you manage, review Discord's permission summary, and finish the authorization flow. If the desired server is missing from the list, your Discord account may not have permission to add applications there.

03

Initial Setup

Connect Vanta's systems to the correct channels, roles, and guild configuration.

/setup
  1. Run /setup.
  2. Select or configure the requested server system.
  3. Choose the correct channel when prompted.
  4. Confirm Vanta can view and send messages in that channel.
  5. Ensure Vanta's role is high enough in the server role hierarchy.
  6. Repeat setup for other systems as needed.

Automatic setup

/autosetup

/autosetup attempts to automatically create or configure supported Vanta systems. Review the created channels, roles, and settings afterward. Setup commands may require elevated permissions such as Server Owner or Administrator depending on the command.

04

Permissions

Vanta needs Discord permissions that match the systems your server uses.

View Channels

Vanta must be able to see channels where commands or configured systems are used.

Send Messages

Required for responses, logs, tickets, and notifications.

Embed Links

Required for Vanta's formatted Discord embeds.

Attach Files

Used where a feature sends files or attachments.

Read Message History

Required for certain moderation and utility functions.

Manage Messages

Required for moderation features that delete or manage messages.

Manage Roles

Required for role-based features. The Vanta role must also be above the roles it manages.

Connect

Required for joining voice channels.

Speak

Required for music playback.

Use Application Commands

Required for slash commands.

Administrator

The current Vanta invite requests Administrator permission. Administrator grants broad access to server features. Only authorize Vanta if you trust the application. Server owners may review requested permissions before authorizing the bot.

05

Commands

Slash commands are organized around core controls and feature categories.

/help

Shows available Vanta commands.

/setup

Configures supported Vanta systems.

/autosetup

Automatically configures supported systems where available.

/ping

Checks Vanta's responsiveness.

/invite

Displays Vanta's bot invitation and support links.

Command categories

Moderation

Safety and member-management workflows.

Music

Voice playback, queue, and player controls.

Tickets

Member support and private help workflows.

Giveaways

Community giveaway creation and management.

Utilities

Useful server and member tools.

Fun

Entertainment and community interaction.

Server Configuration

Guild-specific setup and system controls.

Exact feature commands can change as Vanta develops. Use /help inside Discord for the commands currently registered for your server.

06

Moderation

Moderation tools depend on both the command user's access and Vanta's Discord permissions.

Before using a moderation workflow, confirm Vanta can view the channel, send messages, read relevant history, and manage messages or roles when the action requires it. Discord role hierarchy always applies: Vanta cannot act on roles or members positioned above its own highest role.

Use /help to view the moderation commands currently available. If a command reports missing permissions, follow the named permission and role-hierarchy checks in Troubleshooting.

07

Music

Vanta uses Lavalink for Discord voice playback and player operations.

Typical music concepts include joining voice, loading tracks, search, queue management, pause, resume, skip, stop, volume, loop, and shuffle. Use /help for the exact music commands currently available.

Spotify integration

Spotify links may be used for metadata or search resolution depending on configuration. Actual Discord audio playback is handled through Lavalink-supported audio sources; Spotify does not necessarily provide the audio stream.

Source availability

Third-party music providers can change APIs, authentication systems, or playback restrictions. A temporary source outage does not always mean Vanta itself is offline. Try another track or source before contacting support.

08

Tickets

Ticket systems need valid channels, categories, staff roles, and channel-management access.

Complete ticket setup, keep the configured staff role available, and ensure Vanta can create or access the necessary channels. Depending on the configured workflow, Vanta may need Manage Channels, View Channel, Send Messages, Embed Links, and Manage Roles.

09

Logging

Logging sends configured guild events to a channel selected by server administrators.

The log channel must continue to exist and allow Vanta to view it, send messages, and embed links. If the channel is deleted or its permissions change, run the relevant setup flow again and select a valid destination.

10

Giveaways

Giveaways rely on valid options and permission to post in the selected channel.

Confirm the command user has the required access, Vanta can send embeds in the giveaway channel, and supplied duration and winner values are valid. Test in another channel to distinguish a channel override from a wider configuration issue.

11

Roles

Reaction roles and auto roles are controlled by Discord's role hierarchy.

Move Vanta's highest role above every role it needs to assign or remove, and grant Manage Roles. Vanta cannot manage the server owner's role or any role above its own. Reconfigure reaction roles if the original configured message was deleted.

12

Welcome System

Welcome and leave systems post member events to a configured guild channel.

Select a channel that Vanta can view and post in. Grant Send Messages and Embed Links, then check category overrides. If a configured channel is deleted or moved into a restricted category, repeat setup with a valid channel.

13

Integrations

Vanta connects supported features to external APIs without publishing private credentials.

Spotify

Metadata and search resolution for supported music links.

GIPHY

GIF discovery and sharing in supported commands.

Top.gg

Connection to Vanta's public bot listing ecosystem.

AI features

Smart capabilities in supported, configured workflows.

Discord API

Commands, events, permissions, guilds, and voice connectivity.

REST APIs

Structured communication with supported third-party services.

Provider APIs, authentication requirements, and availability can change independently. Vanta never displays private integration tokens through public commands or this website.

14

Troubleshooting

Open an issue below for symptoms, likely causes, complete fixes, and escalation guidance.

01Vanta does not respond to commands

Symptoms

  • A slash command is used but no response appears.
  • Vanta appears online but ignores commands.

Likely causes

Channel permissions, application-command permissions, user access, Discord client issues, or a command-specific problem.

Step-by-step fixes

  1. Verify Vanta is online in the Discord member list.
  2. Make sure Vanta can view the channel.
  3. Make sure Vanta has Send Messages permission.
  4. Verify Use Application Commands is allowed.
  5. Try /ping.
  6. Try the command in another text channel.
  7. Check whether the command requires administrator, moderator, or server-owner permissions.
  8. Check Discord's service status if commands across multiple bots are failing.
  9. Restart Discord if the slash command UI appears broken.
  10. If Vanta responds to /ping but not another command, report that specific command to support.

When to contact support

Contact support if the issue affects multiple channels and permissions are confirmed correct.

02Slash commands are missing

Likely causes

An outdated invite, delayed Discord command registration, a client issue, or the bot no longer being installed.

Step-by-step fixes

  1. Confirm Vanta was invited with the applications.commands scope.
  2. Remove and re-add Vanta if it was installed using an outdated invite.
  3. Restart Discord.
  4. Test on Discord desktop or web.
  5. Check whether slash commands appear in another server.
  6. Make sure the bot is still installed in the server.
  7. Wait briefly after a new bot update because Discord command registration can take time.
  8. If commands remain missing, contact Vanta support.

When to contact support

Contact support after testing another client and confirming Vanta is installed.

03Vanta cannot send messages

Likely causes

A channel or category permission override is preventing Vanta from responding.

Step-by-step fixes

  1. Open the affected channel settings.
  2. Check Permissions.
  3. Confirm Vanta or its role has View Channel.
  4. Confirm Vanta has Send Messages.
  5. Confirm Vanta has Embed Links.
  6. Check category-level overrides.
  7. Check whether another role explicitly denies the permission.
  8. Move Vanta's role higher if role hierarchy is affecting a feature.
  9. Retry /ping in the channel.

When to contact support

Contact support if /ping fails after all channel and category permissions are corrected.

04Vanta cannot manage roles

Likely causes

Discord only allows a bot to manage roles below the bot's highest role.

Step-by-step fixes

  1. Open Server Settings.
  2. Open Roles.
  3. Locate Vanta's role.
  4. Move Vanta's role above every role it needs to manage.
  5. Confirm Manage Roles is enabled.
  6. Check channel-specific permission overrides if applicable.
  7. Remember that Vanta cannot manage the server owner's role.
  8. Vanta cannot manage roles above its own role.
  9. Retry the role command.

When to contact support

Contact support if the target role is below Vanta and Manage Roles is enabled.

05Vanta cannot join a voice channel

Likely causes

Missing voice permissions, channel limits, category overrides, or the user not being in voice.

Step-by-step fixes

  1. Verify the user is currently in a voice channel.
  2. Confirm Vanta can View Channel.
  3. Confirm Vanta has Connect permission.
  4. Check whether the voice channel is full.
  5. Check user limits.
  6. Check category permissions.
  7. Check whether Vanta is server-muted or restricted.
  8. Try another voice channel.
  9. Run the music command again.
  10. If Vanta cannot join any voice channel, contact support.

When to contact support

Contact support when Vanta cannot join any available voice channel.

06Vanta joins voice but no music plays

Likely causes

Missing Speak permission, a muted connection, an unavailable track, or a third-party music-source issue.

Step-by-step fixes

  1. Confirm Vanta has Speak permission.
  2. Make sure Vanta is not server-muted.
  3. Confirm your own Discord audio is not muted.
  4. Verify the selected track or source is available.
  5. Try another song.
  6. Try searching by song title instead of using a direct link.
  7. Try another voice channel.
  8. Check whether music services are experiencing an outage.
  9. Try /stop and reconnect the music player.
  10. If every song fails, contact support.

When to contact support

Contact support if every source fails. YouTube or Spotify can temporarily change playback behavior.

07Music starts and then stops

Symptoms

  • Vanta begins playing normally and stops before the song ends.

Likely causes

A changed permission, manual disconnect, upstream media restriction, or Lavalink playback issue.

Step-by-step fixes

  1. Try a different song.
  2. Try a different source.
  3. Confirm the bot did not lose Connect or Speak permission.
  4. Check whether Vanta was manually disconnected.
  5. Confirm the voice channel did not change permissions while playing.
  6. Retry playback.
  7. Check for a known music-source outage.
  8. If multiple songs stop at a similar point, an upstream media-source or Lavalink playback issue is more likely than a Discord permission issue.
  9. Wait and retry later if the music provider is experiencing playback restrictions.
  10. Contact support with the approximate time, song or source, whether the bot left, and whether every song is affected.

When to contact support

Never send bot tokens, OAuth tokens, Lavalink passwords, or internal credentials with a report.

08Bot leaves the voice channel

Likely causes

Playback ended with an error, a user disconnected Vanta, or voice permissions changed.

Step-by-step fixes

  1. Confirm whether playback stopped first.
  2. Check whether someone used a disconnect or stop command.
  3. Confirm Vanta still has Connect permission.
  4. Verify the channel was not deleted or changed.
  5. Try another voice channel.
  6. Try another song.
  7. Reconnect the bot.
  8. If it consistently leaves after playback errors, contact support.

When to contact support

Contact support if the behavior repeats across channels and songs.

09No Lavalink node available

Likely causes

This is generally an internal Vanta infrastructure issue, not a server configuration problem.

Step-by-step fixes

  1. Retry the music command after a short delay.
  2. Try another song.
  3. Check the Vanta status section.
  4. Do not repeatedly remove and re-add the bot.
  5. Contact support if the issue persists.

When to contact support

Users do not need Lavalink credentials. Support can investigate the service connection.

10YouTube source unavailable

Likely causes

YouTube frequently changes playback systems, and automated media clients can temporarily require updates.

Step-by-step fixes

  1. Try another YouTube video.
  2. Search by song name instead of using a shortened URL.
  3. Try a different source if available.
  4. Check Vanta service status.
  5. Wait and retry later.
  6. If all YouTube tracks fail, report the issue in the support server.

When to contact support

Report a source-wide failure rather than a single unavailable or restricted video.

11Spotify link does not play

Likely causes

Spotify links may provide metadata for search resolution rather than direct Discord audio.

Step-by-step fixes

  1. Confirm the Spotify link is valid.
  2. Try searching using the song title and artist.
  3. Remember that Spotify links may be used for metadata rather than direct audio playback.
  4. Vanta may resolve the Spotify song to another playable source.
  5. Try another Spotify track.
  6. If every Spotify link fails, contact support.

When to contact support

Contact support if valid links consistently fail to resolve.

12Setup command is denied

Likely causes

The command needs elevated guild permissions or is being run outside a server.

Step-by-step fixes

  1. Confirm you are the server owner or have the required permissions.
  2. Verify Administrator permission if required.
  3. Confirm you are running the command inside a guild and not in DMs.
  4. Try /help to verify the bot is responding.
  5. Ask the server owner to complete setup if permission is denied.
  6. Contact support if the server owner is also denied.

When to contact support

Contact support if the server owner receives the same denial.

13Logging channel does not receive logs

Likely causes

The configured channel changed, was deleted, or no longer allows Vanta to post embeds.

Step-by-step fixes

  1. Verify the log channel still exists.
  2. Re-run the appropriate setup option.
  3. Confirm Vanta can View Channel.
  4. Confirm Vanta can Send Messages.
  5. Confirm Embed Links.
  6. Check category overrides.
  7. Trigger a test action if available.
  8. Reconfigure the channel if it was renamed, moved, or deleted.
  9. Contact support if configuration appears correct but logs never arrive.

When to contact support

Contact support with the affected log type and channel name.

14Ticket system does not work

Likely causes

Incomplete setup, deleted channels or roles, or missing channel-management permissions.

Step-by-step fixes

  1. Verify ticket setup was completed.
  2. Confirm the ticket category or channel still exists.
  3. Confirm Vanta can Manage Channels if the system requires channel creation.
  4. Confirm Vanta can View Channel.
  5. Confirm Send Messages.
  6. Confirm Manage Roles if ticket permissions depend on roles.
  7. Check that the configured staff role still exists.
  8. Re-run ticket setup if configuration was changed.
  9. Contact support if ticket creation still fails.

When to contact support

Contact support after confirming the configured category and staff role still exist.

15Giveaway system does not work

Likely causes

Invalid options, user permissions, or missing channel message permissions.

Step-by-step fixes

  1. Confirm Vanta can send messages in the giveaway channel.
  2. Verify Embed Links.
  3. Check that the command user has the required permissions.
  4. Confirm duration and winner values are valid.
  5. Check whether the giveaway channel was removed.
  6. Retry using a different test channel.
  7. Contact support if giveaways cannot be created anywhere.

When to contact support

Contact support if valid giveaways fail in multiple channels.

16Welcome or leave messages do not send

Likely causes

A stale channel configuration or denied message permissions.

Step-by-step fixes

  1. Verify the configured welcome or leave channel exists.
  2. Re-run setup if necessary.
  3. Check View Channel.
  4. Check Send Messages.
  5. Check Embed Links.
  6. Make sure category overrides do not deny Vanta.
  7. Test using a temporary account or member if practical.
  8. Contact support if events still do not trigger.

When to contact support

Contact support if the configured channel is valid and both event types fail.

17Reaction roles or auto roles fail

Likely causes

The target role or message changed, or Discord role hierarchy blocks assignment.

Step-by-step fixes

  1. Confirm the target role still exists.
  2. Move Vanta's role above the target role.
  3. Confirm Manage Roles.
  4. Check that the configured message and channel still exist.
  5. Check channel permissions.
  6. Reconfigure the role system if the original message was deleted.
  7. Retry.
  8. Contact support if role assignment continues to fail.

When to contact support

Contact support when role hierarchy and configuration are confirmed correct.

18Vanta appears offline

Likely causes

A Vanta outage, a Discord outage, or the bot being removed from one server.

Step-by-step fixes

  1. Wait a few minutes.
  2. Check the support server or status section.
  3. Confirm Discord itself is operational.
  4. Do not repeatedly remove and re-add Vanta.
  5. If Vanta is offline globally, wait for service restoration.
  6. If Vanta is online elsewhere but missing from your server, verify it was not kicked or banned.
  7. Reinvite Vanta if necessary.

When to contact support

Contact support if Vanta is available elsewhere but remains offline in your server.

19Database or internal error

Symptoms

  • Vanta reports “Internal error,” “Database error,” or “Something went wrong.”

Likely causes

A temporary internal service, database, or command-processing failure.

Step-by-step fixes

  1. Retry the command once.
  2. Wait briefly and retry.
  3. Do not spam the command.
  4. Check Vanta status.
  5. Contact support if it persists.
  6. Include the command used, approximate time, server name, a screenshot, and what you were trying to do.

When to contact support

Never send a Discord bot token, database password, OAuth refresh token, webhook token, or Lavalink password.

20Discord API outage

Symptoms

  • Multiple bots fail.
  • Slash commands are slow.
  • Messages are delayed.
  • Voice connections fail.

Likely causes

Discord's public API or voice infrastructure may be degraded.

Step-by-step fixes

  1. Check Discord's public service status.
  2. Wait for Discord service restoration.
  3. Do not repeatedly reinstall Vanta.
  4. Retry once Discord services recover.

When to contact support

Vanta support cannot restore Discord services, but can help confirm whether an issue is platform-wide.

21Command says missing permissions

Likely causes

A required guild permission, channel override, or role-hierarchy condition is missing.

Step-by-step fixes

  1. Read the permission named in the error.
  2. Check Server Settings > Roles > Vanta.
  3. Enable the required permission.
  4. Check channel and category overrides.
  5. Confirm role hierarchy.
  6. Retry the command.
  7. If the permission is already granted, contact support with a screenshot.

When to contact support

Contact support with a screenshot when Discord shows the permission is already granted.

15

FAQ

Direct answers to common questions about Vanta.

Is Vanta free?

No pricing information is currently published on this site. Check the support server for current availability and service information.

Can Vanta be used in multiple servers?

Yes. Vanta is designed to operate in multiple Discord servers at the same time.

Why does Vanta request Administrator?

The current invite requests Administrator so supported systems can be configured without a fragmented permission set. Administrator is broad access; review the request and only authorize Vanta if you trust the application.

Does Vanta store server data?

Vanta uses MySQL to maintain configuration and guild-specific data needed for supported systems.

Can one server see another server's configuration?

No. Guild configuration is separated and associated with the Discord server where it was created.

Why does music sometimes stop?

Voice permissions, media-source restrictions, provider outages, or Lavalink playback issues can interrupt a track. Use the troubleshooting steps before reporting the issue.

Does Spotify provide the audio?

Not necessarily. Spotify links may be used for metadata and search resolution while playback is handled through a Lavalink-supported audio source.

Why are slash commands missing?

The bot may have been invited without the applications.commands scope, Discord registration may be delayed, or the local Discord client may need to restart.

Who develops Vanta?

Vanta is developed and maintained by Kruiger Labs. Taz is the owner and lead developer.

Where can I get support?

Start with this documentation. If the issue remains, join the official Vanta support server.

16

Support

Use the docs first, then bring a clear, safe report to the support server.

A useful report includes the command used, approximate time, server name, a screenshot of the visible error, and what you were trying to do. Never include passwords, bot tokens, OAuth tokens, database credentials, webhook tokens, Lavalink passwords, or other private credentials.

Join Support Server Support checklist