> For the complete documentation index, see [llms.txt](https://docs.nexus.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexus.bot/guides/create-a-discord-bot.md).

# Dedicated Instance Setup

Dedicated instances of Nexus Bot require a separate Discord bot created by you.

### 1. Create your application

Open the [Discord Developer Portal](https://discord.com/developers/applications), sign in, and click **New Application**. Enter your bot’s name, review Discord’s terms, then click **Create**. Discord creates the bot user automatically.

![Create your application](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MLdEj1zzd3YvwG1ITZm%2Fuploads%2FvLigCxTbZm0PBnpEQiNQ%2Fclipboard.jpeg?alt=media\&token=eb9c0d36-a183-4adf-b25e-7fa724ae7781)

### 2. Set the name and get your token

Open **Bot** in the sidebar. Set the **Username** and upload your icon. Under **Token**, click **Reset Token**, complete any verification, and copy the new token immediately. It is shown only once.

**Already running?** Resetting the token invalidates the old one. Only reset an existing Nexus bot with Nexus staff’s help. Keep your token private; share it only in your private Nexus setup ticket.

![Bot username and token controls](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MLdEj1zzd3YvwG1ITZm%2Fuploads%2F6ckGtqTI4Be55xyVSuCe%2Fclipboard.jpeg?alt=media\&token=777c9004-57d4-4f1d-9e4d-384ee4be50d8)

### 3. Enable the required intents

On **Bot → Privileged Gateway Intents**, enable **Server Members Intent** and **Message Content Intent**, then click **Save Changes**. Presence Intent is not required by the current Nexus bot. Leave **Requires OAuth2 Code Grant** off.

![Enable Server Members and Message Content intents](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MLdEj1zzd3YvwG1ITZm%2Fuploads%2FUFlxLoaJXbG7Bx2n1bVy%2Fclipboard.jpeg?alt=media\&token=52f9ef36-82c7-4e10-b129-97039d784ea1)

### 4. Configure the server install

Open **Installation**. Ensure **Guild Install** is enabled; User Install is not needed for Nexus. Select **Discord Provided Link** under Install Link. Keep **Public Bot** enabled on the Bot page when using this provided link.

![Installation contexts and install link](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MLdEj1zzd3YvwG1ITZm%2Fuploads%2FD6lxtIINMneP1khZZCds%2Fclipboard.jpeg?alt=media\&token=0d8c88dd-8894-4182-8aec-3a85ad4aacb4)

Under **Default Install Settings → Guild Install**, add both `bot` and `applications.commands`. For the standard Nexus setup, select **Administrator** under Permissions. This grants full server access; ask Nexus staff if you need a restricted permission setup. Save your changes.

![Guild Install scopes and permissions](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MLdEj1zzd3YvwG1ITZm%2Fuploads%2F35pX5AdC3IxBiJmTp0XZ%2Fclipboard.jpeg?alt=media\&token=d470aa40-9daa-4a3e-a1db-be0335490a99)

### 5. Invite the bot and finish setup

Copy your **Install Link**, open it, choose **Add to Server** if prompted, and select your server. You need permission to manage that server.

Open a private setup ticket in the [Nexus support server](https://discord.gg/JNGD7eDsUU) and send your token, install link, and server ID to Nexus staff. The bot stays offline until Nexus configures and starts your dedicated instance.

Once staff confirm it is online, type `/help` to check slash commands. Move the bot’s role above roles it needs to manage. If slash commands are missing, see [Slash Command Setup](https://docs.nexus.bot/guides/slash-command-setup).

Checked against the Discord Developer Portal on 4 October 2026.
