- 
+ 
-
Premium | Premium | Whitelabel | -|--|--|--|--|--| -| Unlimited Tickets | X | X | X | X | -| Automatic Ticket Archives | X | X | X | X | -| Forms | X | X | X | X | -| Ticket Claiming | X | X | X | X | -| Access Control | X | X | X | X | -| Access to Autoclose | OnΒ Leave | On Leave | X | X | -| Max Ticket Panels | 3 | 3 | Unlimited | Unlimited | -| Panel Support Hours | 1 | 1 | Unlimited | Unlimited | -| Message Branding Removal | - | Welcome Message | X | X | -| Access to Statistics | - | X | X | X | -| Awaiting Response Category | - | - | X | X | -| Exit Surveys | - | - | X | X | -| Customise Embed Colour | - | - | X | X | -| Live Message Updates on the Dashboard | - | - | X | X | -| Send Messages Directly from the Dashboard | - | - | X | X | -| Custom Tag Alias | - | - | X | X | -| Customize Bot Name | - | - | - | X | -| Customize Bot Avatar | - | - | - | X | -| Customize Bot Status | - | - | - | X | diff --git a/src/premium/whitelabel-setup-guide.md b/src/premium/whitelabel-setup-guide.md deleted file mode 100644 index 95ddff0..0000000 --- a/src/premium/whitelabel-setup-guide.md +++ /dev/null @@ -1,96 +0,0 @@ -# Whitelabel Setup Guide -*** - -Thanks for purchasing whitelabel and supporting us! - -Please follow this guide **very carefully**. If you skip a single step, the process will not work. The setup is short, and will only need to be done once. - - -## (Step 1 of 5) Link Patreon Account -If you haven't done so already, you'll need to link your Patreon and Discord accounts on [this page](https://www.patreon.com/settings/apps). - -Patreon has a longer guide on how to do this [here](https://support.patreon.com/hc/en-us/articles/212052266-Get-my-Discord-role). - - -## (Step 2 of 5) Create Bot -Next, you'll need to create your custom bot that Tickets will run under. - -To do this, visit the [Discord developer portal](https://discord.com/developers/applications) and press `New Application` in the top right: - - - -Enter a name for your bot and press create. - -From here, you can change your bot's avatar: - - - - -## (Step 3 of 5) Start Bot -Next, you have to submit the bot's token. This is like a password to the bot. **Never send this token to anyone, even in our support server.** - -Click on `Bot` on the sidebar of the Discord developer portal and copy the token (you may have to click the `reset token` button before you can copy): - - - -Then head over to the Tickets dashboard [Whitelabel section](https://dashboard.tickets.bot/whitelabel). Paste the token into the `Bot Token` field and press `Submit`: - -> **Note:** -> - There may be up to a 10 minute delay for the whitelabel section of dashboard to recognize your status. -> - Until it does, it will lead you back to the "buy premium/whitelabel" page. - - - -You will then be presented with a message saying that the bot is now online. - -If you receive an error, make sure that you copied the token (not the client secret) fully. Additionally, refresh the page and check the `Error Log` table for any errors. - - -## (Step 4 of 5) Invite Bot To Server -Before you can invite the bot to your server, you must kick the main `Tickets v2#5105` bot from your server. It is **extremely** important that you do this **before** inviting your custom bot to your server. If you do not do this, you risk data loss. - - - -To invite your whitelabel bot to your server, click the `Generate Invite Link` button under the Manage Bot section. - -Upon clicking the button, you will be taken to the normal bot invite page - select your server and authorise. It is important that you grant the bot all the permissions that it asks for. - - - - -## (Step 5 of 5) Activate Premium Perks -The last mandatory step is to activate the premium perks that come with whitelabel for your server. - -> **Note:** -> - There may be up to a 10 minute delay for the whitelabel bot to recognize the guild/server and synch commands. -> - Until it does, it will error when running commands. -> - If command errors, wait 10 minutes and try the command again. - -Go to your discord server and run the command `/premium`. You must select the command when it displays to you after typing. Make sure to choose `patreon` since that is how you paid for the whitelabel bot. **Giveaway Key is not used here.** - -- *If `Patreon` is not a selectable option, then your premium perks are already applied to the server.* - - - -**And you're done!** Your bot should be ready for use. - -There are a few more **optional** steps below, if you wish to take them. - - -## Optional: Set Custom Status -You can optionally change your custom bot's status. Simply enter the new status on the dashboard and press `Submit`. - -`Playing`, `Listening`, `Watching`, `Competing` and `Custom` are all currently available. - - - - -## Optional: Set Privacy Policy & ToS Links -On the `General Information` tab of the Discord developer portal, you may have noticed `Terms Of Service URL` and `Privacy Policy URL` fields. - -You should enter our policies here to inform users of how their data may be used. - -**Terms Of Service:** https://tickets.bot/terms-of-service -**Privacy Policy:** https://tickets.bot/privacy - - diff --git a/src/setup/auto.md b/src/setup/auto.md deleted file mode 100644 index e353d41..0000000 --- a/src/setup/auto.md +++ /dev/null @@ -1,14 +0,0 @@ -# Bot Configuration: Automatic Setup -*** - -Tickets provides an option to automatically create a basic configuration for you. This isn't recommended since the settings are unlikely to be to your preference, and a ticket panel is **not** automatically created. For information on creating ticket panels, see our guide [here](./panels.md). - -To run the automatic setup mode, first ensure that you are either the owner of the server, or the owner has designated you as an administrator of the bot using `/addadmin @YourUsername`. Next, simply execute `/setup auto` in a channel the bot can see. - -It will update you as the process progresses: - - - -Simply assign your support staff the new `Tickets Support` role and your administrators the `Tickets Admin` role and your staff will be able to open and support users in tickets created via `/open` or the context menu (right click > apps > start ticket.) - -You'll probably want to [create a ticket panel](./panels.md) so it's easier for your server members to open a ticket, or tweak the settings on the [web dashboard](./dashboard.md). \ No newline at end of file diff --git a/src/setup/configuration.md b/src/setup/configuration.md deleted file mode 100644 index baa0f2d..0000000 --- a/src/setup/configuration.md +++ /dev/null @@ -1,27 +0,0 @@ -# Bot Configuration -*** - -Let's start getting the bot ready for use in your server! - -Tickets was a very early adopter of slash commands, meaning that you can simply hit `/` in your Discord client to have commands auto-completed with the correct arguments: - - - -If you're not the owner of the server, now would be a good time to get the owner to designate you as an admin of Tickets. You can do this by asking the owner to run the command `/addadmin @YourUsername` in a channel the bot can see. If successful, Tickets will show you a β . - -We've created a few different ways in which you can configure the bot: -- Via the [web dashboard](https://dashboard.tickets.bot) **[Recommended]** -- Via `/setup` - - Auto - - Individual Settings - -> **Note:** We recommend using the web dashboard to configure the bot, as it's easier and more settings are available - including ticket panels. - -If you'd prefer to stick to configuring the bot via commands in Discord, there are a few different methods in which you can do so: -- `/setup auto` will automatically create roles, channels, and everything else you need (excluding reaction panels) without any interaction required from you. This is okay for simple usecases, but you'll likely want to configure the options yourself. -- **Individual Settings**: Run commands such as `/setup limit` and `/setup use-threads` to change individual settings one by one. - -We have guides on each of the available methods: -- [Web Dashboard](./dashboard.md) **[Recommended]** -- [Auto](./auto.md) -- [Individual Settings](./individual.md) diff --git a/src/setup/dashboard.md b/src/setup/dashboard.md deleted file mode 100644 index 1838da8..0000000 --- a/src/setup/dashboard.md +++ /dev/null @@ -1,93 +0,0 @@ -# Bot Configuration: Web Dashboard -*** - -First, head over to the dashboard at [dashboard.tickets.bot](https://dashboard.tickets.bot). You'll be asked to login with Discord - simply click `Authorize` and you'll be taken back to the dashboard. - - - -A list of servers which you are a Tickets bot administrator (`/addadmin`) and the bot has been invited to should show up. Simply click on the server you want to configure. If the server does not show up, ensure that you are either the owner of the server or have been added as a Tickets bot administrator by the owner using `/addadmin @YourUsername` and log out of, then back into, the dashboard. - - - -You'll be taken to the settings page as follows: - - - -You'll first want to pay attention to the main **Settings** card. Here you can edit the following settings: - -## Per User Simultaneous Ticket Limit - -This is the amount of tickets that a **single user** can have open **at a single time**. We usually recommend setting this to 1, but the default is 5. - -For example, if you set this value to 1, a user will be able to open and close tickets an infinite amount of times, but only have a single ticket open at once. This value does not affect the total amount of tickets that can be opened at once in a server. - -We do not impose any limits on the amount of tickets that a server can have open at once. However, please note that Discord only permits a total of 500 channels to exist in a server at once, and 50 channels to exist at once in a category. This means that you can move tickets to a new category if one gets filled, however you are limited to 500 channels overall by Discord. - -## Allow Users To Close Tickets - -This option specifies whether users are allowed to close their own tickets. If unchecked, only your support staff & administrators will be able to close them. - -## Ticket Close Confirmation - -This option specifies whether Tickets will send a confirmation message when closing a ticket via the π`close` reaction. If checked, Tickets will send the following message after reacting: - - - -Simply click the blue βοΈ`close` reaction to confirm you want to close the ticket. - -Close confirmation does not apply to tickets closed using the slash command `/close`. - -## Welcome Message - -The welcome message is the message displayed in the Ticket as soon as the user opens it: - - - -> **Note:** the message has a maximum limit of 1024 characters due to Discord limitations. - -- You may make use of placeholders in your welcome message. You can view a list of placeholders [here](../miscellaneous/placeholders.md). - -- You may also use discord message formatting to include links to channels, emojis, roles, or usernames in your welcome message. **First**, you will need to have discord developer mode turned on - in your personal discord account settings > advanced > discord developer mode. **Second**, you can right click any channel name, username, message, etc and choose `Copy ID`. **Third**, use the `structure` section of [discord's messge formatting chart](https://discord.com/developers/docs/reference#message-formatting) to include it in your welcome message. - -The title of the embed will either be based off of the subject provided by the user when using `/open [Subject]`, or the title of the ticket panel if used. We are unable to get a subject from the user when using ticket panels currently, however, this will be possible in a future update of Discord. - -## Transcripts Channel - -When Tickets are closed, a transcript will automatically be recorded, encrypted, and stored in cloud based object storage - with no user interaction required. - -A message, similar to the one following, will also be sent to your transcripts channel to notify you the ticket was closed and provide you with a link to the dashboard to view the archive: - - - -This message will also be sent via direct messages to the user who opened the ticket. It is not possible to disable this functionality since we believe it is important for transparency purposes that users are also able to access the transcripts. - -If you have privacy concerns, please join our [support server](https://discord.gg/ticketsbot) to enquire. Unfortunately we are unable to answer any questions regarding your user data off-platform in order to verify your identity. - -## Channel Category - -Designates the channel category that tickets will be created under. If you are unsure what a channel category is, Discord has a guide explaining them available [here](https://support.discord.com/hc/en-us/articles/115001580171-Channel-Categories-101). - -Your tickets will be grouped together under the category as follows: - - - -## Overflow Category - -Discord has an imposed limitation that each Channel Category can only hold 50 channels. Once you hit this limit, Tickets bot will fail to be able to open more ticket channels for you and your server members. To help rectify this, you can set an Overflow Category. This is a category that the ticket channels will open in once your selected Channel Category has hit the Discord imposed limit. - -## Naming Scheme - -Defines how the ticket channels should be named. Currently, the 2 options are by ticket ID (`#ticket-1`) or by username (`#ticket-name`). You can define more [custom naming schemes](./panels.md#naming-scheme) in the settings of individual reaction panels, instead of this overall setting. - -## Submission - -Once you are satisfied with your settings, press the `Submit` button to save them. An example follows: - - - -We now have the basic configuration completed! - -You may wish to configure the following options next: -- [Ticket Panels](./panels.md) -- [Claim Settings](../dashboard/settings/claiming.md) -- [Auto Close](../dashboard/settings/settings.md/#auto-close) diff --git a/src/setup/individual.md b/src/setup/individual.md deleted file mode 100644 index fb87824..0000000 --- a/src/setup/individual.md +++ /dev/null @@ -1,42 +0,0 @@ -# Bot Configuration: Indiviual Commands -*** - -You can also tweak individual settings by using a single command. Note, not all settings are available via command, some are only accessible on the [dashboard](./dashboard.md), such as [ticket panels](./panels.md). - -To run the setup, first ensure that you are either the owner of the server, or the owner has designated you as an administrator of the bot by using `/addadmin @YourUsername`. - -For definitions and explanations of settings, please refer to the [dashboard guide](./dashboard.md#ticket-limit). - -## Setup Commands - -| Command | Description | -| ---------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | -| /setup auto | Bot will make a very basic configuration (no ticket panels - you'll still want to customize on dashboard) | -| /setup limit | Change the quantity of tickets a single user can have open at the same time | -| /setup transcripts | Change the transcripts channel | -| /setup use-threads | Change whether thread mode is enabled | - -### Auto -See our guide on auto setup [here](./auto.md). - -### Ticket Limit -An explanation of ticket limits is available [here](./dashboard.md#ticket-limit). The command `/setup limit` is used to configure the ticket limit. - -> **For example:** to change the per user simultaneous ticket limit to `1` **-** Run `/setup limit 1` - -### Transcripts -An explanation of transcript channels is available [here](./dashboard.md#transcripts-channel). The command `/setup transcripts` is used to configure the transcripts channel. - -> **For example:** to change the transcripts channel to `#logs` **-** Run `/setup transcripts #logs` - -- _Please note, the channel must already exist._ - -### Use Threads -It is recommended to read an explanation of thread mode (and how it compares to channel mode) [here](../features/thread-mode.md) before using this command. The command `/setup use-threads` is used to enable (`true`), or disable (`false`), whether tickets open as private threads instead of channels. It will also be necessary to select the ticket notification channel. - -> **For example:** to enable thread mode **-** Run `/setup use-threads`, choose `true`, click `ticket_notification_channel`, then select the channel desired from list - -- _Please note, the selected channel must already exist._ - -## Additional Settings -Additional settings are available on the [dashboard](./dashboard.md), such as [ticket panels](./panels.md). It is advised that you read these guides next. diff --git a/src/setup/introduction.md b/src/setup/introduction.md deleted file mode 100644 index 39d1393..0000000 --- a/src/setup/introduction.md +++ /dev/null @@ -1,27 +0,0 @@ -# Setup -*** - -Thanks for choosing Tickets as your support solution! In this guide we'll teach you how to get up and running in no time at all. - -> If you need any assistance in the process, feel free to join our [Discord server](https://discord.com/invite/ticketsbot) and open a ticket to talk to our support staff. - -### For those with previous experience configuring Discord bots -*** -Quickly get the absolute basic functions of a ticket system for your server in 5 steps: - -**1.** [Invite the bot](https://invite.tickets.bot) -**2.** Make yourself admin of the bot `/addadmin @YourUsername` -**3.** Go to the [web dashboard](https://dashboard.tickets.bot) -**4.** Make a [ticket panel](../setup/panels.md) -**5.** Go back to discord and add your staff as support so they can see and answer tickets `/addsupport @TheirRole` - -> It is **HIGHLY RECOMMENDED** to continue reading through SETUP and the rest of the documentation, as these steps only provide the most basic working ticket system. There are many ways to customize the system, messages, notifications, and support staff. - -### For beginners with Discord bots -*** - -You'll need to start by inviting Tickets to your server. -- *Learn how to do this [here](../setup/invite.md).* - -**If you've already invited the bot to your server**, feel free to jump ahead and start configuring it. -- *View our guide on this [here](../setup/configuration.md).* diff --git a/src/setup/panels.md b/src/setup/panels.md deleted file mode 120000 index 628512f..0000000 --- a/src/setup/panels.md +++ /dev/null @@ -1 +0,0 @@ -../dashboard/reaction-panels.md \ No newline at end of file diff --git a/src/setup/staff.md b/src/setup/staff.md deleted file mode 100644 index 1479e87..0000000 --- a/src/setup/staff.md +++ /dev/null @@ -1,26 +0,0 @@ -# Support Staff -*** - -Now that the ticket system is in place, Tickets bot needs to know which of your staff should have access to the tickets (and the online dashboard settings - if desired.) - -> **There are two scenarios for how to setup support staff:** -> - Staff members handle **SPECIFIC** tickets -> - Staff members handle **ALL** tickets - - -## Staff members handle SPECIFIC tickets -*** -> Setting the support staff in this scenario can only be accomplished via the [web dashboard](https://dashboard.tickets.bot). A guide on this can be found [here](../dashboard/staff-teams.md). - - -## Staff members handle ALL tickets -> Setting the support staff in this scenario, is recommended via slash commands. - -**Command:** `/addadmin @username` or `/addadmin @role` - -Not only does this add the specified user to the Default Team in Staff Teams, but it also gives that user full administrative privileges of the Tickets bot for your server. This is just having admin of the Tickets bot, **not your server**. -- Having admin privileges of the bot means the user will be able to use the [web dashboard](https://dashboard.tickets.bot) fully, and control all the configuration, settings, customization of the bot, as well as see ALL of the tickets/transcripts contained there. ***Only give this privilege to those you trust.*** - -**Command:** `/addsupport @username` or `/addsupport @role` - -This adds the specified user to the Default Team in Staff Teams. The only thing they will be able to see on the web dashboard are the tickets where the Default Team has been assigned as a support team. diff --git a/src/vid/Forms.mp4 b/src/vid/Forms.mp4 deleted file mode 100644 index ea2ad0d..0000000 Binary files a/src/vid/Forms.mp4 and /dev/null differ diff --git a/src/vid/ReactionPanels.mp4 b/src/vid/ReactionPanels.mp4 deleted file mode 100644 index 4e63e09..0000000 Binary files a/src/vid/ReactionPanels.mp4 and /dev/null differ diff --git a/src/vid/StaffTeams.mp4 b/src/vid/StaffTeams.mp4 deleted file mode 100644 index 0f62b61..0000000 Binary files a/src/vid/StaffTeams.mp4 and /dev/null differ diff --git a/theme/favicon.svg b/theme/favicon.svg deleted file mode 100644 index 4d9c4c3..0000000 Binary files a/theme/favicon.svg and /dev/null differ
+
-Tickets v2 Documentation
+Tickets Documentation
- All documentation for the Discord bot "Tickets v2"
+ All documentation for the Discord bot "Tickets"
Explore the docs Β»
@@ -71,9 +71,9 @@
## About The Project
-
+
-User-facing documentation for [Tickets v2](https://tickets.bot). Tickets is a simple, customisable, and powerful Discord ticket system bot complete with a web UI.
+User-facing documentation for [Tickets](https://tickets.bot). Tickets is a simple, customisable, and powerful Discord ticket system bot complete with a web UI.
-
- **Warning:** Users in Support Teams are now deprecated. Please migrate to roles.
-
-
-This adds the specified user to the Default Team in Staff Teams. The only thing they will be able to see on the web dashboard are the tickets where the Default Team has been assigned as a support team.
\ No newline at end of file
diff --git a/src/commands/close-requests.md b/src/commands/close-requests.md
deleted file mode 100644
index 076fad3..0000000
--- a/src/commands/close-requests.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# Close Requests
-***
-
-Another unique feature of Tickets is close requests.
-
-When you feel a ticket is able to be closed, you can use the `/closerequest` command to ask the user to confirm they feel everything is resolved:
-
-
-
-If the user chooses to deny the request, the message will be updated:
-
-
-
-## Close Delay
-
-Additionally, you can specify a time (in hours) after which the ticket will be closed automatically if the user has not responded, and a reason for closure of the ticket:
-
-
-
-If a close delay is not specified, the ticket will not be closed until the user accepts the request.
-
-> **Note:** If a ticket is excluded from being automatically closed via `/autoclose exclude`, close request delays will not apply, even if provided.
\ No newline at end of file
diff --git a/src/commands/commands.md b/src/commands/commands.md
deleted file mode 100644
index 6f881b5..0000000
--- a/src/commands/commands.md
+++ /dev/null
@@ -1,57 +0,0 @@
-# Command List
-***
-
-| General Commands | Description |
-| -- | -- |
-| /about | Information about the bot |
-| [/gdpr](./gdpr.md) (lang) | Request deletion or anonymization of your data under GDPR |
-| /help | Displays a list of commands |
-| /invite | Provides an invite link for the bot |
-| /vote | Gives a link to vote for free premium beneftis |
-
-| Ticket Commands | Description |
-| -- | -- |
-| /add (user_or_role) | Add a user or role to an existing ticket |
-| /claim | Assigns a single staff member to the current ticket |
-| /close (reason) | Closes the current ticket |
-| [/closerequest](../features/close-requests.md) (close_delay) (reason) | Sends a message asking the ticket opener to approve or deny closing of the ticket |
-| /jumptotop | Displays a button to click and will automatically scroll to the top of the ticket |
-| /on-call | Toggles whether the user of command will be added and pinged to all new thread mode tickets |
-| /open (subject) | Opens a new ticket |
-| /remove (user_or_role) | Removes a user or role from the current ticket |
-| /rename (new_ticket_name) | Renames the current ticket |
-| /reopen (ticket ID) | reopens a thread ticket that was previously closed |
-| /switchpanel (to_panel) | Switches the current ticket to another ticket panel - changing the channel category, support teams, etc |
-| /transfer (user) | Transfers a claimed ticket to another user |
-| /unclaim | Removes the claim on the current ticket |
-| /notes | Creates a private thread for staff to talk in, only works in channel mode |
-
-| Setting Commands | Description |
-| -- | -- |
-| [/addadmin](./add-admin-support.md) (user_or_role) | Grants a user or role admin priveledges of the bot |
-| [/addsupport](./add-admin-support.md) (user_or_role) | Adds a user or role as a support representative |
-| /autoclose configure | Edit autoclose related settings |
-| /autoclose exclude | Excludes the current ticket from being automatically closed |
-| /blacklist (user_or_role) | Toggles whether users are allowed to interact with the bot |
-| /language (language) | Changes the language the bot messages are displayed in |
-| /panel | Provides a link to create a reaction panel for users to open tickets |
-| /premium | Activates premium benefits after purchasing (choose patreon on select menu) |
-| /removeadmin (user_or_role) | Revokes a user's or role's admin priveledges |
-| /removesupport (user_or_role) | Revokes a user's or role's support representative priviledges |
-| /setup auto | Bot will make a very basic configuration (no reaction panels - you'll still want to customize on dashboard) |
-| /setup limit | Change the quantity of tickets a single user can have open at the same time |
-| /setup transcripts | Change the transcripts channel |
-| /setup use-threads | Toggle if the bot creates new threads or new channels |
-| /viewstaff | Lists the staff members and roles (admin or support) |
-
-| Tag Commands | Description |
-| -- | -- |
-| /managetags add | Adds a new tag |
-| /managetags delete | Deletes a tag |
-| /managetags list | Lists all existing tags |
-| /tag (tag_id) | Sends a message snippet |
-
-| Statistics Commands | Description |
-| -- | -- |
-| /stats user | Displays statistics about the selected user |
-| /stats server | Displays statistics about the server |
diff --git a/src/commands/introduction.md b/src/commands/introduction.md
deleted file mode 100644
index 6e8adda..0000000
--- a/src/commands/introduction.md
+++ /dev/null
@@ -1,4 +0,0 @@
-# Commands
-This chapter provides some information regarding key commands.
-
-Use the sidebar to navigate this chapter.
\ No newline at end of file
diff --git a/src/dashboard/blacklist.md b/src/dashboard/blacklist.md
deleted file mode 100644
index 1e874dd..0000000
--- a/src/dashboard/blacklist.md
+++ /dev/null
@@ -1,40 +0,0 @@
-# Blacklist
-***
-
-Upon opening the `Blacklist` tab, there will be one main area that displays two buttons and any users/roles that have been blacklisted in your discord server.
-
-
-
-## Blacklist New User
-To blacklist an individual user from being able to open a ticket, use this button. Once clicked, a new window will appear with a search input.
-
-
-
-Start typing the username here and select it when found.
-
-
-
-Once the selection is confirmed, a success message will display and the username and ID will be displayed under the `Blacklisted User` section.
-
-
-
-
-### Notes
-
-- Users can also be found by their ID, rather than their username. The `USE USER ID` toggle can be flipped to green and the user ID search input will appear. Paste the user ID here and hit `Confirm` to blacklist.
-- User ID's can be found if you have turned on the Discord Developer Mode. This can be found in your user settings.
- - Right click any username and choose `Copy ID`
-
-
-
-#### Blacklist New Role
-To blacklist a role from being able to open a ticket, use this button. Once clicked, a new window will appear with a search input.
-
-- This is very similar to blacklisting an individual user.
-
-#### Role / User
-Those who have been blacklisted will appear in these sections.
-
-- Any role/user can be allowed to make tickets again by removing them from the blacklist by clicking the corresponding `Remove` button next to the role/username.
-
-
diff --git a/src/dashboard/forms.md b/src/dashboard/forms.md
deleted file mode 100644
index a9c2449..0000000
--- a/src/dashboard/forms.md
+++ /dev/null
@@ -1,51 +0,0 @@
-# Forms
-***
-
-Tickets has the ability to prompt users for answers to pre-defined questions when opening a ticket:
-
-
-
-To set this up, a form must first be created and then applied to a [Ticket Panel](../dashboard/reaction-panels.md). It is possible to assign a single form to multiple different types of tickets.
-
-## Basic Video Walkthrough
-
-
-## Creating the Form
-First, head over to the [web dashboard](https://dashboard.tickets.bot) and select your server.
-
-Then, select the `Forms` tab in the navigation bar:
-
-
-
-You can now create your first form. Enter a name for it, and press `Create`:
-
-
-
-Next, select your form from the `Manage Forms` dropdown list, and add up to 5 inputs. Enter a label for the question, some placeholder text, and select the type of input:
-
-
-
-> **Note the discord imposed limitations for forms:**
-> - Maximum of 5 inputs per form
-> - Currently only supports text input style - no radio buttons, or checkboxes
-> - Maximum character limits
-> - Name - 45
-> - Labels - 45
-> - Placeholder - 100
-
-Make sure to save your inputs.
-Your form has now been created. In order to show it to users, you must assign it to a `Ticket Panel`.
-
-## Assign Form to a Panel
-Head over to the `Ticket Panels` page of the dashboard via the top navigation bar, as shown in the [panels](../setup/panels.md) documentation.
-
-Either create a new ticket panel, or choose an existing one to edit. You will notice a dropdown labeled `Form`. Expand this dropdown, and select your new form:
-
-
-
-Save your changes, and then test it out!
-
-
-
-## Multipanels
-When using [multi-panels](./multipanels.md) (different types of tickets combined into 1 message with multiple buttons), the form shown to the user is the form associated to the panel of the button clicked.
diff --git a/src/dashboard/introduction.md b/src/dashboard/introduction.md
deleted file mode 100644
index c3ac70f..0000000
--- a/src/dashboard/introduction.md
+++ /dev/null
@@ -1,4 +0,0 @@
-# Dashboard
-This chapter provides information regarding configuring the bot using the web dashboard.
-
-Use the sidebar to navigate this chapter.
\ No newline at end of file
diff --git a/src/dashboard/multipanels.md b/src/dashboard/multipanels.md
deleted file mode 100644
index 28d7169..0000000
--- a/src/dashboard/multipanels.md
+++ /dev/null
@@ -1,74 +0,0 @@
-# Multi Panels
-***
-
-Multi-panels are the combination of 2 or more Ticket Panels in a single embed:
-
-
-
-## Creating A Multi-panel
-In order to create a multi-panel, you'll need to head over to the web dashboard and select your server. If you're unfamiliar with how to do that, read our [guide on the web dashboard here](../setup/dashboard.md).
-
-Once on your server's main settings page, select `Ticket Panels` in the navigation bar:
-
-
-
-You'll want to focus on the *right* side of the screen. The left side are settings for individual panels (known as [Ticket Panels](../dashboard/reaction-panels.md).)
-
-Draw your attention to the `New Multi-Panel` card. You'll configure the panel's appearance here:
-
-
-
-### Panel Title
-The panel title is the bold text at the _top_ of the embed.
-
-> **Note:** The panel title has a maximum length of 255 characters, and by default, it is set to `Open a ticket!`.
-
-### Panel Content
-The panel content is the text in the long description of the embed. We recommend providing a general overview of how your support system works, such as which languages the support agents are fluent in.
-
-> **Note:** The panel content has a maximum length of 1024 characters.
-
-### Panel Colour
-This is the colour on the left side of the embed. When clicked, a colour picker will open as shown below:
-
-
-
-### Panel Channel
-This is the channel that the multi-panel will be sent in for users to react to. Therefore, this channel should be accessible to your users, and be the only message in the channel to avoid confusion.
-
-**This should not be the same as your archive / transcript channel.**
-
-### Panels
-This input field is where you select which of your already made individual panels you'd like to include in the multi-panel.
-
-### Use Dropdown Menu
-- **Unchecked** = Ticket options appear as clickable buttons.
-- **Checked** = Ticket options appear as a dropdown menu.
-
-## Advanced Settings
-Upon clicking `Toggle Advanced Settings`, you'll have extra fields displayed to you:
-- [Large Image URL](#large-image-url)
-- [Small Image URL](#small-image-url)
-
-### Large Image URL
-Input a URL link to an image here, it will be shown **underneath the welcome message**.
-- *File path MUST end in .png - easy trick is to send the image as a message in a discord channel, then right click the message and choose "Copy Link." Paste link into the input.*
-
-### Small Image URL
-Input a URL link to an image here, it will be shown to the **right of the welcome message**.
-- *File path MUST end in .png - easy trick is to send the image as a message in a discord channel, then right click the message and choose "Copy Link." Paste link into the input.*
-
-## Completion
-Once you have configured the multi-panel to your liking, click `Submit` and the panel will be created in your server. You should be shown a success message in the bottom right hand corner of your screen if successful, or an appropriate error message if you made a mistake:
-
-
-
-- If you leave any fields blank, the default values will be used.
-
-## Editing
-If you wish to update a multi-panel at a later date, simply click the edit button in the list of multi-panels and the editing modal will be opened:
-
-
-
-
-You can also delete a multi-panel by clicking the `Delete` button, or deleting the message containing the multi-panel in Discord. If you only delete the message in Discord, the multi-panel will continue to exist on your Dashboard and you can resubmit it to Discord if needed.
diff --git a/src/dashboard/reaction-panels.md b/src/dashboard/reaction-panels.md
deleted file mode 100644
index 4883c4b..0000000
--- a/src/dashboard/reaction-panels.md
+++ /dev/null
@@ -1,178 +0,0 @@
-# Panels
-***
-## Basic Video Walkthrough
-
-
-# Creating A Panel
-In order to create a ticket panel, head over to the web dashboard and select your server. If unfamiliar with how to do that, read our [guide on the web dashboard here](../setup/dashboard.md).
-
-Once on your server's main settings page, select `Ticket Panels` in the navigation bar to be taken to the ticket panel configuration page which looks as follows:
-
-
-
-Focus on the _left_ side of the screen. The right side are settings for combining different panels into a single message.
-
-Draw your attention to the `New Panel` card. Configure the panel's appearance here:
-
-
-
-
-## Ticket Properties
-***
-
-
-### Mention On Open
-Specify a list of roles/users to mention after the ticket is opened.
-
-> **Note:** This will not work for those who have their notification settings on mute.
-
-### Support Teams
-Input which `Staff Teams` will handle tickets created from this reaction panel.
-
-### Ticket Category
-Designates the channel category that the ticket channel will be created under. If unsure of what a channel category is, Discord has a guide explaining them available [here](https://support.discord.com/hc/en-us/articles/115001580171-Channel-Categories-101).
-
-Ticket panels use different channel categories to the one configured on the main settings tab to allow for distinction when using multiple reaction panels - meaning it is possible to have each "type" of ticket open in it's own category for easier organization.
-
-### Form
-Assign a form to the panel.
-
-- _Learn more about Forms [here](../features/forms.md)._
-
-### Naming Scheme
-This toggle can be used to change the naming scheme of the ticket channels. If it's left on green, it will use the naming scheme set in the `Settings` portion of the Dashboard. If it's flipped to grey, a custom scheme can be setup.
-
-- Placeholders can be used in the custom naming scheme. View a list of placeholders [here](../miscellaneous/placeholders.md#custom-naming-scheme-placeholders).
-
-### Exit Survey Form
-
-Users can be requested to leave feedback when their ticket is closed.
-
-- _Learn more about Exit Surveys [here](../dashboard/settings/exit-survey.md)._
-
-> **Note:** This is a premium feature. Learn more about premium [here](https://tickets.bot/premium).
-
-### Awaiting Response Category
-Tickets awaiting a user's response can be moved to a different category.
-
-- _Learn more about Awaiting Response Category [here](../dashboard/settings/awaiting-response.md)._
-
-> **Note:** This is a premium feature. Learn more about premium [here](https://tickets.bot/premium).
-
-### Cooldown
-Set a per-user cooldown (in seconds) to prevent users from opening multiple tickets on the same panel in quick succession. When a user opens a ticket, they must wait for the cooldown period to elapse before they can open another ticket on this panel.
-
-- A value of `0` disables the cooldown (default).
-- Staff members (Support role and above) are exempt from cooldowns.
-- Cooldowns are tracked per user, per panel β different panels can have different cooldown durations.
-- Admins can reset all active cooldowns for a panel from the dashboard using the `Reset Cooldowns` button.
-
-### Hide Claim Button
-Toggle whether the `Claim` button is shown in tickets opened from this panel. This overrides the server-wide default set in the Settings page.
-
-- _Learn more about Claiming [here](../dashboard/settings/claiming.md)._
-
-### Hide Close Button
-Toggle whether the `Close` button is shown in tickets opened from this panel. This overrides the server-wide default set in the Settings page.
-
-### Hide Close with Reason Button
-Toggle whether the `Close with Reason` button is shown in tickets opened from this panel. This overrides the server-wide default set in the Settings page.
-
-### Support Hours
-Configure time-based restrictions on when tickets can be opened from this panel. Support hours are configured per day of the week with a start and end time in a timezone of your choice.
-
-- _Learn more about Support Hours [here](../features/support-hours.md)._
-
-> **Note:** Free servers can configure support hours on 1 panel. Premium servers have no limit. Learn more about premium [here](https://tickets.bot/premium).
-
-## Panel Message
-***
-
-### Panel Title
-The panel title is the bold text at the _top_ of the embed.
-
-> **Note:** The panel title has a maximum length of 255 characters, and by default, it is set to `Open a ticket!`.
-
-### Panel Content
-The panel content is the text in the long description of the embed. We recommend providing a general overview of how your support system works, such as which languages the support agents are fluent in.
-
-> **Note:** The panel content has a maximum length of 1024 characters.
-
-### Panel Colour
-This is the colour on the left side of the embed. When clicked, a colour picker will open as shown below:
-
-
-
-### Panel Channel
-This is the channel that the ticket panel will be sent in for users to react to. Therefore, this channel should be accessible to all members, and be the only message in the channel to avoid confusion.
-
-> **Note:** This should **NOT** be the same as your transcript channel.
-
-### Disable Panel
-Enable this checkbox to disable users from opening tickets from this panel.
-
-### Button Colour
-Choose the colour of the button.
-
-### Button Text
-Enter the text that the button will contain.
-
-### Button Emoji
-This is the emoji that users will click in order to open a ticket. The emoji can either be pasted directly into the box, for example: `π©`, or the Discord name can be used, for example: `envelope_with_arrow` (colons are optional.)
-
-Custom emojis from your server can be used by clicking the toggle to show green instead of grey. When toggled on, the input field will show you a list of your available emojis to choose from.
-
-### Large Image URL
-Input a URL link to an image here, it will display **underneath the welcome message**.
-
-
-- _File path MUST end in .png - easy trick is to send the image as a message in a discord channel, then right click the message and choose "Copy Link." Paste link into the input._
-
-### Small Image URL
-Input a URL link to an image here, it will display to the **right of the welcome message**.
-
-
-- _File path MUST end in .png - easy trick is to send the image as a message in a discord channel, then right click the message and choose "Copy Link." Paste link into the input._
-
-
-## Welcome Message
-***
-
-The server's welcome message can be overridden on a per-panel basis using this field. If left blank, the welcome message from the main settings page will be used.
-
-> **Note:** the message has a maximum limit of 4096 characters due to Discord limitations.
-
-- Placeholders can be used in the welcome message. View a list of placeholders [here](../miscellaneous/placeholders.md).
-
-- Discord message formatting can also be used to include links to channels, emojis, roles, or usernames in the welcome message.
- - **First**, discord developer mode must be turned on - in your personal discord account settings > advanced > discord developer mode.
- - **Second**, right click any channel name, username, message, etc and choose `Copy ID`.
- - **Third**, use the `structure` section of [discord's messge formatting chart](https://discord.com/developers/docs/reference#message-formatting) to include it in the welcome message.
-
-## Access Control
-***
-
-You can now specify a list of roles that can / can't open a ticket with each panel. The access control list is evaluated from top-to-bottom, stopping after the first match.
-
-In the image below only users with the `Whitelabel`, `Patrons`, or `Nitro Booster` roles can open tickets, but not if they have the `Muted` role.
-
-
-
-
-## Completion
-***
-
-Once the ticket panel has been configured, click `Create` and the panel will be created in the server. A success message should be shown in the bottom right hand corner of the screen if successful, or an appropriate error message if there was a mistake:
-
-
-
-- If any fields are left blank, the default values will be used.
-
-
-## Editing
-***
-
-Ticket panels can be edited at a later date. Simply click the `Edit` button in the list of panels and the editing modal will be opened:
-
-
-A panel can also be deleted by clicking the `Delete` button, or deleting the message containing the panel in Discord. If only the message in Discord is deleted, the panel will continue to exist on the Web Dashboard and can be resubmitted to Discord if needed, by clicking the `Resend` button.
diff --git a/src/dashboard/settings/awaiting-response.md b/src/dashboard/settings/awaiting-response.md
deleted file mode 100644
index 8512d9f..0000000
--- a/src/dashboard/settings/awaiting-response.md
+++ /dev/null
@@ -1,15 +0,0 @@
-# Awaiting User Response
-***
-
-Setting a category for ticket channels which are awaiting the user's response to be moved to. This feature is highly useful for being able to tell which tickets require a response from staff members, and reduces clutter in your ticket categories.
-
-> **Note:** Channel mode only. Discord does not allow threads to be moved. For more differences between the two modes, click [here](./thread-mode.md#channel-vs-thread-comparison).
-
-
-
-
-This setting can be controlled for each `Ticket Panel` individually. The ticket channel will be moved to the awaiting response category 10 minutes after the last response from a staff member.
-
-Due to Discord limitations, a channel can only be updated twice every 10 minutes, so it is not possible to change how quickly the channel gets moved to the awaiting response category.
-
-> **Note:** This feature is only for servers that have premium activiated. Learn more about premium [here](https://tickets.bot/premium).
\ No newline at end of file
diff --git a/src/dashboard/settings/claiming.md b/src/dashboard/settings/claiming.md
deleted file mode 100644
index e582299..0000000
--- a/src/dashboard/settings/claiming.md
+++ /dev/null
@@ -1,33 +0,0 @@
-# Claiming
-***
-
-> **Note:** Channel mode only. Discord does not allow threads to be claimed. For more differences between the two modes, click [here](./thread-mode.md#channel-vs-thread-comparison).
-
-Tickets can be claimed by a staff member, so other staff members cannot also reply to the ticket. The benefit of this is that tickets become less cluttered with many staff members talking at once.
-Alternatively, an admin could claim a ticket to keep the support team from seeing potentially sensitive issues.
-
-> **Note:** Those with Administrator permissions in your server will always have access to any claimed ticket, as well as the user who claimed it.
-
-## Commands Related to Claiming
-- **/claim** - Assigns you to a ticket
-- **/transfer @User** - Transfers a claimed ticket to another user
-- **/unclaim** - Removes the claim on the current ticket
-
-## Claiming can be configured in 3 ways
-- All staff members can see the ticket, but only the claimer can reply (Default)
-- All staff members can see the ticket, and all staff members can reply
-- Only the claimer can see the ticket
-
-## Panel Switch Behavior
-When a claimed ticket is switched to a different panel using `/switchpanel`, the claimer may not have access to the new panel's support team. This setting controls what happens in that scenario:
-
-- **Auto Unclaim** (Default) - The ticket is automatically unclaimed when switched to a panel the claimer doesn't have access to
-- **Block Switch** - Prevents switching to a panel if the claimer doesn't have access to it. The ticket must be unclaimed first before switching
-- **Remove On Unclaim** - Allows the switch, but removes the claimer's access to the ticket when they unclaim it
-- **Keep Access** - Allows the switch and keeps the claimer's access to the ticket even after unclaiming
-
-> **Note:** This setting only applies when the claimer doesn't have access to the new panel. If the claimer has access to both panels, the ticket remains claimed and no special handling is needed.
-
-You can configure these settings on the dashboard's settings tab:
-
-
diff --git a/src/dashboard/settings/exit-survey.md b/src/dashboard/settings/exit-survey.md
deleted file mode 100644
index e28e396..0000000
--- a/src/dashboard/settings/exit-survey.md
+++ /dev/null
@@ -1,14 +0,0 @@
-# Exit Survey
-***
-
-Users can be requested to leave feedback when their ticket is closed.
-
-## Enable Exit Survey
-1. Ensure [user feedback](feedback.md#enabling-feedback) (star rating) is enabled
-2. Create a [form](../../features/forms.md), as you normally would, but enter your feedback questions
-3. Edit your [panels](../../setup/panels.md) and set the `Exit Survey Form` input to this new form
-
-The next time a user rates a ticket, they will also be prompted to fill out the feedback form.
-
-## View Exit Survey Responses
-When a user leaves a survey response, the archive message in your `Transcript Channel` will be updated with a button to view their response.
\ No newline at end of file
diff --git a/src/dashboard/settings/feedback.md b/src/dashboard/settings/feedback.md
deleted file mode 100644
index 814959e..0000000
--- a/src/dashboard/settings/feedback.md
+++ /dev/null
@@ -1,36 +0,0 @@
-# Feedback
-***
-
-Tickets allows your users to provide feedback on the support they received:
-
-
-## Enabling Feedback
-In order for users to be asked to rate your service, you must first enable feedback on the [web dashboard](https://dashboard.tickets.bot/).
-
-Select your server and open the settings page:
-
-
-Check the `Enable User Feedback` box and press submit.
-Next time a user closes a ticket, they will be asked for feedback.
-
-## Viewing Feedback
-There are several ways to view feedback:
-
-### Server Stats
-If you are a [premium](https://tickets.bot/premium) subscriber, you can view your feedback statistics with `/stats server`:
-
-
-### User Stats
-If you are a [premium](https://tickets.bot/premium) subscriber, you can use `/stats user` to view the average rating on tickets claimed by a specific user:
-
-
-### Placeholders
-You can include the following placeholders in your welcome message to display your feedback rating to users:
-- %average_rating%
-- %rating_count%
-
-> **Note:** View more placeholders by clicking [here](./placeholders.md).
-
-### Viewing Individual Ticket Ratings
-You can view the ratings of individual tickets by navigating to the transcripts page on the dashboard. Next to each ticket, the rating given by the user will be shown:
-
diff --git a/src/dashboard/settings/placeholders.md b/src/dashboard/settings/placeholders.md
deleted file mode 120000
index 9cf4312..0000000
--- a/src/dashboard/settings/placeholders.md
+++ /dev/null
@@ -1 +0,0 @@
-../../miscellaneous/placeholders.md
\ No newline at end of file
diff --git a/src/dashboard/settings/settings.md b/src/dashboard/settings/settings.md
deleted file mode 100644
index 12899a3..0000000
--- a/src/dashboard/settings/settings.md
+++ /dev/null
@@ -1,166 +0,0 @@
-# Settings
-***
-
-Upon opening the `Settings` tab, extra sections will be displayed (with the first two being expanded):
-
-- [General](#general)
-- [Thread Mode](#thread-mode)
-- [Tickets](#tickets)
-- [/Open Command](#open-command)
-- [Context Menu (Start Ticket Dropdown)](#context-menu-start-ticket-dropdown)
-- [Claiming](#claiming)
-- [Auto Close](#auto-close)
-- [Ticket Permissions](#ticket-permissions)
-- [Colour Scheme](#colour-scheme)
-
-
-
-## General
-Here you will find settings that affect the entire server, not just a specific ticket panel.
-
-### Per User Simultaneous Ticket Limit
-Set the max amount of tickets a server member can have open at one time (staff is immune to this limit.)
-
-- _This is total number of tickets **per member**, not per panel._
-
-### Language
-Set the bot's language.
-
-- _Learn more about Language Customization [here](../../setup/languages.md)._
-
-### Allow Users To Close Tickets
-Toggle whether the server members that open tickets can close them (or if that will be a permission only given to staff.)
-
-### Ticket Close Confirmation
-Toggle whether a second confirmation is required to close a ticket.
-
-
-
-### Enable User Feedback
-Toggle whether a user can provide a star rating feedback on the service they received.
-
-- _Learn more about User Feedback [here](../../setup/feedback.md)._
-
-### Anonymise Dashboard Responses
-Check this box to have all responses from the web dashboard come from the bot rather than the support staff.
-
-## Thread Mode
-We now support using private threads for tickets! This is a new optional mode for the bot that drastically changes how tickets operate.
-
-- _Learn more about Thread Mode [here](../../features/thread-mode.md)._
-
-### Enabled
-Toggle whether tickets are created using Channel Mode or Thread Mode.
-
-- _Must be checked for rest of section to work._
-
-### Ticket Notification Channel
-Select which channel should receive the embedded messages containing a notification to your staff that a ticket has been opened. This same message will also have a button for your staff to click and join the ticket thread.
-
-## Tickets
-This section has a few more optional settings.
-
-### Transcripts Channel
-Select if/which channel should receive an embedded message containing a summary of each closed ticket. If you have also chosen to store transcripts (see below) there will also be a link to the transcript. Only those who had access to the ticket (plus all those with administration permissions in the server) will be able to access it.
-
-
-
-### Overflow Category
-Discord has a limit of 50 channels to a category (and 500 channels total per server), so here is where another category can be selected for tickets to go into if the first Ticket Category is full.
-
-- _Learn more about Ticket Category [here](../reaction-panels.md#ticket-category)._
-
-### Store Ticket Transcripts
-Toggle whether transcripts of each ticket are stored for later review by your staff.
-
-### Hide Claim Button
-Toggle whether the `Claim` button is shown in each ticket.
-
-- _Learn more about Claiming [here](./claiming.md)._
-
-### Hide Close Button
-Toggle whether the `Close` button is shown in each ticket's welcome message. When enabled, the close button will be removed, though users and staff can still close tickets via the `/close` command.
-
-- _This setting acts as the server-wide default. It can be overridden on a per-panel basis in the panel's Ticket Properties._
-
-### Hide Close with Reason Button
-Toggle whether the `Close with Reason` button is shown in each ticket's welcome message. When enabled, the close with reason button will be removed, though users and staff can still close tickets with a reason via the `/close` command.
-
-- _This setting acts as the server-wide default. It can be overridden on a per-panel basis in the panel's Ticket Properties._
-
-## /Open Command
-This section has settings when using the `/open` command to create a ticket.
-
-### Disable /Open Command
-Toggle whether server members can use `/open` to create a ticket.
-
-### Channel Category
-Select which category the open tickets will display.
-
-### Naming Scheme
-Select a naming scheme:
-Ticket followed by numbers or Ticket followed by the username of opener.
-
-### Welcome Message
-The welcome message is the message displayed in the Ticket as soon as the user opens it:
-
-
-
-> **Note:** the message has a maximum limit of 4096 characters due to Discord limitations.
-
-- Placeholders can be used in the welcome message. View a list of placeholders [here](./placeholders.md).
-
-- Discord message formatting can also be used to include links to channels, emojis, roles, or usernames in the welcome message.
- - **First**, discord developer mode must be turned on - in your personal discord account settings > advanced > discord developer mode.
- - **Second**, right click any channel name, username, message, etc and choose `Copy ID`.
- - **Third**, use the `structure` section of [discord's messge formatting chart](https://discord.com/developers/docs/reference#message-formatting) to include it in the welcome message.
-
-The title of the embed will either be based off of the subject provided by the user when using `/open [Subject]`, or the title will show "No subject given" if one wasn't input.
-
-## Context Menu (Start Ticket Dropdown)
-This section has settings dealing with tickets that are created via the context menu (right clicking a message.)
-
-- There is a dedicated page documenting this section [here](../../features/start-ticket-from-message.md).
-
-## Claiming
-This section has the settings dealing with claiming tickets.
-
-- There is a dedicated page documenting this section/feature [here](./claiming.md).
-
-## Auto Close
-This section has settings dealing with automated closing of tickets.
-
-### Enabled
-Toggle whether any auto-close features work or not.
-
-- _Must be checked for rest of section to work._
-
-### Close On User Leave
-Toggle whether you'd like open tickets to be automatically closed if the Ticket Opener leaves the server.
-
-### Since Open With No Response
-Set a timeframe in the boxes. If Ticket Opener does not type a message within that timeframe, the ticket will be closed automatically.
-
-- _This is a premium feature. Learn more about premium [here](https://tickets.bot/premium)._
-
-### Since Last Message
-Set a timeframe in the boxes. If no messages occur within that timeframe, the ticket will be closed automatically.
-
-- _This is a premium feature. Learn more about premium [here](https://tickets.bot/premium)._
-
-## Ticket Permissions
-In this area you can define if some permissions are given to the users who open tickets.
-
-- **Green toggle buttons** - user **will** receive this permission in their respective ticket channel.
-- **Grey toggle buttons** - user **will not** receive this permission in their respective ticket channel.
-
-## Colour Scheme
-Select custom colours for the embedded messages from Tickets bot.
-
-- _This is a premium feature. Learn more about premium [here](https://tickets.bot/premium)._
-
-## Completion
-Once you have configured these settings to your liking, click `Submit` for them to take effect in your server.
-
-## Editing
-If you wish to update your settings at a later date, simply change the desired settings and click `Submit` again.
diff --git a/src/dashboard/settings/start-ticket-from-message.md b/src/dashboard/settings/start-ticket-from-message.md
deleted file mode 120000
index 70c945b..0000000
--- a/src/dashboard/settings/start-ticket-from-message.md
+++ /dev/null
@@ -1 +0,0 @@
-../../features/start-ticket-from-message.md
\ No newline at end of file
diff --git a/src/dashboard/settings/thread-mode.md b/src/dashboard/settings/thread-mode.md
deleted file mode 120000
index 0ee0d44..0000000
--- a/src/dashboard/settings/thread-mode.md
+++ /dev/null
@@ -1 +0,0 @@
-../../features/thread-mode.md
\ No newline at end of file
diff --git a/src/dashboard/staff-teams.md b/src/dashboard/staff-teams.md
deleted file mode 100644
index 9b1333d..0000000
--- a/src/dashboard/staff-teams.md
+++ /dev/null
@@ -1,51 +0,0 @@
-# Staff Teams
-***
-
-Staff Teams can be used to further customize which of your staff members can see, claim, respond to, and close specific types of tickets. This is possible because Staff Teams get linked to individual ticket panels however you see fit. Click to learn more about [ticket panels](../dashboard/reaction-panels.md) or the [support teams input](../dashboard/reaction-panels.md/#support-teams).
-
-## Basic Video Walkthrough
-
-
-## Primary View
-Upon opening the `Staff Teams` menu, there will be two main areas displayed:
-- [Create Team](#create-team)
-- [Manage Teams](#manage-teams)
-
-
-
-## Create Team
-Create new Staff Teams here by typing in a team name and clicking `Submit`.
-- *A team must exist before it can be managed.*
-
-## Manage Teams
-Options for managing a team:
-- [Staff Teams](#staff-teams)
- - [Basic Video Walkthrough](#basic-video-walkthrough)
- - [Primary View](#primary-view)
- - [Create Team](#create-team)
- - [Manage Teams](#manage-teams)
- - [Delete a Staff Team](#delete-a-staff-team)
- - [Add Members / Roles to a Staff Team](#add-members--roles-to-a-staff-team)
- - [Remove Members / Roles from a Staff Team](#remove-members--roles-from-a-staff-team)
- - [Default Team](#default-team)
-
-
-
-### Delete a Staff Team
-Select the team you wish to delete, and a red `Delete` button will appear next to #1 of photo above.
-
-### Add Members / Roles to a Staff Team
-- **Select** the team in which you wish to add the members/roles (**#1**)
-- **Search** for the member or role you wish to add (**#3**) and click `+ Add To Team`
-- **Member/Role will appear** in area **#2** of photo above
-
-### Remove Members / Roles from a Staff Team
-- **Select** the team in which you wish to remove the members/roles (**#1**)
-- **Click** `Delete` button next to the name of member/role to remove, in area **#2** of photo above
-
-
-
-## Default Team
-The Default team cannot be deleted. Those members/roles added with the `/addadmin` and `/addsupport` commands get added to this team automatically.
-- *Learn more about these two commands [here](../commands/add-admin-support.md).*
-- *Learn more about the rest of the commands [here](../commands/commands.md)*
diff --git a/src/dashboard/tags.md b/src/dashboard/tags.md
deleted file mode 100644
index 46e4c1c..0000000
--- a/src/dashboard/tags.md
+++ /dev/null
@@ -1,117 +0,0 @@
-# Tags
-***
-
-Tags are pre-defined snippets of text sent by the bot. These can be useful for quickly sending responses to commonly asked questions or concerns.
-
-## Primary View
-Upon opening the `Tags` menu, there will be one main area that displays any tags that have been created and a button to create new tags.
-
-
-
-When there are created tags, each tag name will show and some action buttons - `Edit` and `Delete`
-
-
-
-## Creating a Tag
-Clicking the `+ Create Tag` button will bring up the Tag Editor.
-
-
-
-### Tag ID
-This is the "name" of the tag and what will be used in the command (i.e. if ID is "docs", command is `/tag docs`.)
-
-
-
-### Message Content
-This is how the bot will respond when the command is used.
-
-**Note:** Tags support [placeholders](../miscellaneous/placeholders.md) when used in ticket channels. All welcome message placeholders work in tags, allowing you to create dynamic responses with user information, ticket details, and more.
-
-
-
-## Use Embed
-- *Bot responses may also be in customisable embeds complete with images, if desired.*
-
-Flipping the `Use Embed` toggle to green will display some more sections:
-- [Tags](#tags)
- - [Primary View](#primary-view)
- - [Creating a Tag](#creating-a-tag)
- - [Tag ID](#tag-id)
- - [Message Content](#message-content)
- - [Use Embed](#use-embed)
- - [Embed](#embed)
- - [Author](#author)
- - [Images](#images)
- - [Footer](#footer)
- - [Fields](#fields)
- - [Using a Tag](#using-a-tag)
-
-
-
-### Embed
- - **Embed Colour**
- This is the colour on the left side of the embed. When clicked, a colour picker will open as shown below:
-
-
- - **Title**
- The embed title is the bold text at the *top* of the embed. The embed title has a maximum length of 255 characters.
-
- - **Title URL (optional)**
- The embed title can be turned into a hyperlink to a webpage by filling out this input.
-
- - **Description**
- This is the message content of the embed.
-
-### Author
- - **Author Name**
- This will display **above the embed title**.
-
- - **Author Icon URL (optional)**
- This will display to the **left of the author name**.
-
- - **Author URL (optional)**
- The author name can be turned into a hyperlink to a webpage by filling out this input.
-
-### Images
- - **Large Image URL**
- Input a URL link to an image here, it will display at the **bottom of the embed**.
- - *File path MUST end in .png - easy trick is to send the image as a message in a discord channel, then right click the message and choose "Copy Link." Paste link into the input.*
-
- - **Small Image URL**
- Input a URL link to an image here, it will display at the **top right of the embed**.
- - *File path MUST end in .png - easy trick is to send the image as a message in a discord channel, then right click the message and choose "Copy Link." Paste link into the input.*
-
-### Footer
- - **Footer Text**
- Will display **below the Large Image at the bottom of the embed**. This text is a little smaller than the Description.
-
- - **Footer Icon URL (optional)**
- Input a URL link to an image here, it will display to the **left of the Footer Text**.
- - *File path MUST end in .png - easy trick is to send the image as a message in a discord channel, then right click the message and choose "Copy Link." Paste link into the input.*
-
- - **Footer Timestamp (optional)**
- Choose a date here, it will display **after the Footer Text**.
-
-### Fields
- Additional fields can be added to the embed. Think of these as sections. The field name will appear in bold (as a title to the section), and the Field Value is the text within the section.
-
-
-
-*Example tag embed with Fields not inline*
-
- - **Field Name**
- This is the title of the new field section that will appear in the embed. It will display in bold.
-
- - **Inline**
- *Checked* = Fields display horizontally (columns on the same row)
- *Unchecked* = Fields display vertically
-
- - **Field Value**
- This is the description section of the new field that will appear in the embed.
-
-
-
-*Example tag embed with Fields inline*
-
-## Using a Tag
-Within Discord, use the `/tag` command by typing `/tag` and selecting the tag ID from menu, or type the full `/tag [tagname]`
diff --git a/src/dashboard/tickets.md b/src/dashboard/tickets.md
deleted file mode 100644
index ea787de..0000000
--- a/src/dashboard/tickets.md
+++ /dev/null
@@ -1,33 +0,0 @@
-# Ticket List
-***
-
-Upon opening the `Tickets` menu, there will be one main area that displays any open tickets in your discord server.
-
-
-
-## ID
-The unique identification number of the ticket will display.
-
-## Panel
-The ticket panel name of the ticket will display.
-- *Learn more about Ticket Panels [here](./reaction-panels.md).*
-
-## User
-The user who opened the ticket will display.
-
-## View
-Click to view the current state of the ticket.
-
-If we clicked `View` on ticket #15, this would be displayed:
-
-
-
-For comparison, this is the current state of ticket #15 in the discord server:
-
-
-
-The ticket can be closed from this view, with or without a reason specified.
-
-### Premium Perks
-Those with premium, will get real-time updates, be able to respond to messages, and close the ticket in this view.
-- *Learn more about premium [here](https://tickets.bot/premium).*
\ No newline at end of file
diff --git a/src/dashboard/transcripts.md b/src/dashboard/transcripts.md
deleted file mode 100644
index 9e393ec..0000000
--- a/src/dashboard/transcripts.md
+++ /dev/null
@@ -1,32 +0,0 @@
-# Transcripts
-***
-
-Upon opening the `Transcripts` menu, you'll have two cards displayed to you:
-- Filter Logs
-- Transcripts
-
-
-
-## Filter Logs
-Here you can filter the transcripts displayed in the lower Transcripts section.
-
-Fill out the inputs as desired and click `Filter` button.
-
-## Transcripts
-Here you can view transcripts of closed tickets.
-
-### Ticket ID
-This unique ticket number cannot be reset or changed.
-
-### Username
-Discord username of the ticket opener.
-
-### Rating
-If user feedback is enabled, the feedback rating given by ticket opener will display.
-- *Learn more about User Feedback [here](../setup/feedback.md).*
-
-### Close Reason
-If `close with reason` button was selected (or `/close` was used and a reason was input), it will display. Otherwise, it will display "No reason specified."
-
-### Transcript
-Click to view the transcript.
\ No newline at end of file
diff --git a/src/features/close-requests.md b/src/features/close-requests.md
deleted file mode 100644
index 76b0b2c..0000000
--- a/src/features/close-requests.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# Close Requests
-***
-
-Another unique feature of Tickets is close requests.
-
-When you feel a ticket is able to be closed, you can use the `/closerequest` command to ask the user to confirm they feel everything is resolved:
-
-
-
-If the user chooses to deny the request, the message will be updated:
-
-
-
-## Close Delay
-
-Additionally, you can specify a time (in hours) after which the ticket will be closed automatically if the user has not responded, and a reason for closure of the ticket:
-
-
-
-If a close delay is not specified, the ticket will not be closed until the user accepts the request.
-
-> **Note:** If a ticket is excluded from being automatically closed via `/autoclose exclude`, close request delays will not apply, even if provided.
diff --git a/src/features/feedback.md b/src/features/feedback.md
deleted file mode 100644
index 656d0cb..0000000
--- a/src/features/feedback.md
+++ /dev/null
@@ -1,36 +0,0 @@
-# Feedback
-***
-
-Tickets allows your users to provide feedback on the support they received:
-
-
-## Enabling Feedback
-In order for users to be asked to rate your service, you must first enable feedback on the [web dashboard](https://dashboard.tickets.bot/).
-
-Select your server and open the settings page:
-
-
-Check the `Enable User Feedback` box and press submit.
-Next time a user closes a ticket, they will be asked for feedback.
-
-## Viewing Feedback
-There are several ways to view feedback:
-
-### Server Stats
-If you are a [premium](https://tickets.bot/premium) subscriber, you can view your feedback statistics with `/stats server`:
-
-
-### User Stats
-If you are a [premium](https://tickets.bot/premium) subscriber, you can use `/stats user` to view the average rating on tickets claimed by a specific user:
-
-
-### Placeholders
-You can include the following placeholders in your welcome message to display your feedback rating to users:
-- %average_rating%
-- %rating_count%
-
-> **Note:** View more placeholders by clicking [here](../dashboard/settings/placeholders.md).
-
-### Viewing Individual Ticket Ratings
-You can view the ratings of individual tickets by navigating to the transcripts page on the dashboard. Next to each ticket, the rating given by the user will be shown:
-
diff --git a/src/features/forms.md b/src/features/forms.md
deleted file mode 100644
index 2697ed0..0000000
--- a/src/features/forms.md
+++ /dev/null
@@ -1,51 +0,0 @@
-# Forms
-***
-
-Tickets has the ability to prompt users for answers to pre-defined questions when opening a ticket:
-
-
-
-To set this up, a form must first be created and then applied to a [Ticket Panel](../dashboard/reaction-panels.md). It is possible to assign a single form to multiple different types of tickets.
-
-## Basic Video Walkthrough
-
-
-## Creating the Form
-First, head over to the [dashboard](https://dashboard.tickets.bot) and select your server.
-
-Then, select the `Forms` tab in the navigation bar:
-
-
-
-You can now create your first form. Enter a name for it, and press `Create`:
-
-
-
-Next, select your form from the `Manage Forms` dropdown list, and add up to 5 inputs. Enter a label for the question, some placeholder text, and select the type of input:
-
-
-
-> **Note the discord imposed limitations for forms:**
-> - Maximum of 5 inputs per form
-> - Currently only supports text input style - no radio buttons, or checkboxes
-> - Maximum character limits
-> - Name - 45
-> - Labels - 45
-> - Placeholder - 100
-
-Make sure to save your inputs.
-Your form has now been created. In order to show it to users, you must assign it to a `Ticket Panel`.
-
-## Assign Form to a Panel
-Head over to the `Ticket Panels` page of the dashboard via the top navigation bar, as shown in the [panels](../setup/panels.md) documentation.
-
-Either create a new `Ticket Panel`, or choose an existing one to edit. You will notice a dropdown labeled `Form`. Expand this dropdown, and select your new form:
-
-
-
-Save your changes, and then test it out!
-
-
-
-## Multipanels
-When using [multi-panels](./multipanels) (different types of tickets combined into 1 message with multiple buttons), the form shown to the user is the form associated to the panel of the button clicked.
diff --git a/src/features/introduction.md b/src/features/introduction.md
deleted file mode 100644
index ba0fbda..0000000
--- a/src/features/introduction.md
+++ /dev/null
@@ -1,4 +0,0 @@
-# Features
-This chapter provides some details about the core features of the bot.
-
-Use the sidebar to navigate this chapter.
\ No newline at end of file
diff --git a/src/features/multipanels.md b/src/features/multipanels.md
deleted file mode 100644
index ab5fff5..0000000
--- a/src/features/multipanels.md
+++ /dev/null
@@ -1,76 +0,0 @@
-# Multi Panels
-***
-
-Multi-panels are the combination of 2 or more Ticket Panels in a single embed:
-
-
-
-## Creating A Multi-panel
-In order to create a multi-panel, you'll need to head over to the web dashboard and select your server. If you're unfamiliar with how to do that, read our [guide on the web dashboard here](../setup/dashboard.md).
-
-Once on your server's main settings page, select `Ticket Panels` in the top navigation bar:
-
-
-
-You'll want to focus on the *right* side of the screen. The left side are settings for individual panels (known as [Ticket Panels](../dashboard/reaction-panels.md).)
-
-Draw your attention to the `New Multi-Panel` card. You'll configure the panel's appearance here:
-
-
-
-### Panel Title
-The panel title is the bold text at the _top_ of the embed.
-
-> **Note:** The panel title has a maximum length of 255 characters, and by default, it is set to `Open a ticket!`.
-
-### Panel Content
-The panel content is the text in the long description of the embed. We recommend providing a general overview of how your support system works, such as which languages the support agents are fluent in.
-
-> **Note:** The panel content has a maximum length of 1024 characters.
-
-### Panel Colour
-This is the colour on the left side of the embed. When clicked, a colour picker will open as shown below:
-
-
-
-### Panel Channel
-This is the channel that the multi-panel will be sent in for users to react to. Therefore, this channel should be accessible to your users, and be the only message in the channel to avoid confusion.
-
-**This should not be the same as your archive / transcript channel.**
-
-### Panels
-This input field is where you select which of your already made individual panels you'd like to include in the multi-panel.
-
-### Use Dropdown Menu
-- **Unchecked** = Ticket options appear as clickable buttons.
-- **Checked** = Ticket options appear as a dropdown menu.
-
-## Advanced Settings
-Upon clicking `Toggle Advanced Settings`, you'll have extra fields displayed to you:
-- [Large Image URL](#large-image-url)
-- [Small Image URL](#small-image-url)
-
-### Large Image URL
-Input a URL link to an image here, it will be shown **underneath the welcome message**.
-- *File path MUST end in .png - easy trick is to send the image as a message in a discord channel, then right click the message and choose "Copy Link." Paste link into the input.*
-
-### Small Image URL
-Input a URL link to an image here, it will be shown to the **right of the welcome message**.
-- *File path MUST end in .png - easy trick is to send the image as a message in a discord channel, then right click the message and choose "Copy Link." Paste link into the input.*
-
-## Completion
-***
-
-Once you have configured the multi-panel to your liking, click `Submit` and the panel will be created in your server. You should be shown a success message in the bottom right hand corner of your screen if successful, or an appropriate error message if you made a mistake:
-
-
-
-- If you leave any fields blank, the default values will be used.
-
-## Editing
-If you wish to update a multi-panel at a later date, simply click the edit button in the list of multi-panels and the editing modal will be opened:
-
-
-
-
-You can also delete a multi-panel by clicking the `Delete` button, or deleting the message containing the multi-panel in Discord. If you only delete the message in Discord, the multi-panel will continue to exist on your Dashboard and you can resubmit it to Discord if needed.
\ No newline at end of file
diff --git a/src/features/start-ticket-from-message.md b/src/features/start-ticket-from-message.md
deleted file mode 100644
index b156dd9..0000000
--- a/src/features/start-ticket-from-message.md
+++ /dev/null
@@ -1,35 +0,0 @@
-# Start Ticket From Message
-***
-
-Did you know that you can start a ticket from a channel using message context menus?
-
-This is a similar functionality to Discord private threads. A common use case is for using tickets to perform moderation, where you can drag a user into a ticket to discuss a specific message with them.
-
-## How To Use
-To start a ticket from a message, simply right click the message (or long press on mobile devices), hover over `Apps`, and select `Start Ticket`:
-
-
-
-A new ticket will be created with the user who sent the message. The bot will send a message quoting the user, as well as providing a link to the message:
-
-
-
-## Configuration
-### Required Permission Level
-To limit usage of this functionality to staff members: visit the [web dashboard](../setup/dashboard.md), select your server, and take a look at the `Settings` page.
-
-You will see a dropdown menu labelled `Required Permission Level` under the `Context Menu (Start Ticket Dropdown)` heading. Adjust the setting to your needs, and then press the `Submit` button.
-
-
-
-### Add Message Sender To Ticket
-If you are using this functionality for users to report messages, you may not wish to have the person who is being reported added to the ticket for anonymity.
-
-
-
-This will also stop the `Conversation moved to ticket` message from being sent.
-
-### Use Settings From Panel
-By default, tickets opened via the context menu use the `/open` command settings. If you wish to use the settings of a specific `Ticket Panel`, i.e. so you can use `Mention On Open`, select the panel you wish to use under the `Use Settings From Panel` dropdown.
-
-
diff --git a/src/features/support-hours.md b/src/features/support-hours.md
deleted file mode 100644
index b88c519..0000000
--- a/src/features/support-hours.md
+++ /dev/null
@@ -1,48 +0,0 @@
-# Support Hours
-***
-
-Support hours allow you to restrict when tickets can be opened on a panel. You can configure a schedule for each day of the week with a start and end time, and choose what happens when a user tries to open a ticket outside of those hours.
-
-## Configuration
-
-Support hours are configured per panel. To set them up, edit a panel from the **Ticket Panels** page on the web dashboard and open the **Support Hours** section.
-
-### Timezone
-Select the timezone that your support hours are based on. This should match the timezone your support team operates in. Any valid IANA timezone is supported (e.g. `America/New_York`, `Europe/London`, `UTC`). The dashboard will display the current time in the selected timezone for reference.
-
-### Schedule
-For each day of the week, you can:
-- **Enable or disable** the day β disabled days mean the panel is closed all day.
-- Set a **start time** and **end time** β the window during which tickets can be opened.
-
-If no days are enabled, support hours are effectively disabled and the panel will be available 24/7.
-
-#### Presets
-The dashboard provides quick preset buttons:
-- **Business hours** β sets Monday to Friday, 9:00 - 17:00.
-- **Copy to weekdays** β copies Monday's hours to Tuesday through Friday.
-- **Set 24/7** β clears all restrictions.
-
-## Out-of-Hours Behaviour
-
-When a user tries to open a ticket outside of the configured support hours, the panel's behaviour depends on the **Out-of-Hours Behaviour** setting:
-
-### Block Creation (default)
-The user **cannot** open a ticket. They will be shown an embed with a customisable title, message, and colour explaining that support is currently unavailable.
-
-### Allow with Warning
-The user **can** still open a ticket, but will receive a warning message letting them know that support is currently outside of normal hours and response times may be longer.
-
-## Customisation
-
-You can customise the message shown to users when they interact with the panel outside of support hours:
-
-- **Title** β the embed title (max 100 characters). Defaults to "Support is currently unavailable".
-- **Message** β the embed description (max 500 characters).
-- **Colour** β the embed accent colour.
-
-## Premium
-
-Free servers can configure support hours on **1 panel**. Premium servers can configure support hours on **unlimited panels**.
-
-- _Learn more about premium [here](https://tickets.bot/premium)._
diff --git a/src/features/thread-mode.md b/src/features/thread-mode.md
deleted file mode 100644
index e669c0d..0000000
--- a/src/features/thread-mode.md
+++ /dev/null
@@ -1,63 +0,0 @@
-# Thread Mode
-***
-
-We now support using private threads for tickets! This is a new *optional* mode for the bot that drastically changes how tickets operate.
-
-Instead of the whole support team being added to a ticket when it is opened, the thread starts out with *no staff members*. A button is then sent to your *ticket notification channel* which staff members click to be added to the thread:
-
-
-
-## Channel vs Thread Comparison
-|Channels|Threads|
-|--|--|
-|Can be sorted by category|Attached to the Ticket Panel channel|
-|Can move between categories with `/switchpanel` command|Cannot be moved|
-|Tickets cannot be reopened once closed|Tickets can be reopened|
-|Transcripts only viewable on dashboard|Transcripts viewable on dashboard, and within Discord|
-|Limited to 500 channels total, and only 50 channels in a single category [^note1]|1000 open threads, unlimited closed threads|
-|All staff on support team added to ticket | Staff members must press button to join ticket [^note2]|
-|Tickets can be claimed |Ticket claiming is unsupported [^note3]|
-|`/switchpanel` changes the ticket panel of an existing ticket |`/switchpanel` is unsupported [^note4]|
-|No concept of on-call staff|Staff can be marked as on-call to automatically be pinged and added to tickets|
-|No spaces in channel names|Spaces in channel names permitted: e.g. `Ticket 1234`
-|Can use /notes for a private thread for staff to talk in|Cannot use /notes due to Discord limitation|
-
-[^note1]: This is a Discord imposed limitation for all servers, not the Tickets bot
-
-[^note2]: See workaround in FAQ [here](#can-the-support-team-be-added-to-thread-automatically)
-
-[^note3]: Staff members must individually click a button to join the ticket, so the behaviour is replicated
-
-[^note4]: This is due to Discord's permission management internals being very different for threads
-
-## On-Call
-Thread mode introduces a new command: `/on-call`. When a staff member runs this command, they will be assigned roles marking them as on call, until they run the command again. When a new ticket is opened, the on call roles are pinged in the ticket, instantly adding all currently on call staff members to the ticket.
-
-> **Note:** When a staff member becomes on call, they will **not** be added to any existing tickets. They must join them via the ticket notification channel as normal.
-
-## How do I enable thread mode?
-You can enable threads directly within Discord, by using the command `/setup use-threads`, like so:
-
-
-
-Alternately, you can enable threads via the settings page of the dashboard:
-
-
-
-## FAQ
-### Which mode should I use?
-If you run a server with a small team, we would likely recommend sticking with channel mode. If you run a server with a heavy focus on 1-on-1 support or claiming, we would recommend thread mode. Nevertheless, if you require any of the additional features like reopening tickets, you must use thread mode.
-
-### Can the support team be added to thread automatically?
-Although it is intended for the support team to click the `Join Ticket` button in the embed message of the `Ticket Notification` channel, it is possible to add support staff automatically. This requires those individuals/roles to be in the `Support Team` & be listed in the `Mention On Open` input for the `Ticket Panel`.
-
-### Will channel mode be removed?
-No, both modes will be supported forever. Thread mode is completely optional.
-
-### My users can't type in their support tickets!
-You must grant the "Send Messages in Threads" permission to your @everyone role in the **panel channel**:
-
-
-
-
-
diff --git a/src/img/access_control.webp b/src/img/access_control.webp
deleted file mode 100644
index 159d66e..0000000
Binary files a/src/img/access_control.webp and /dev/null differ
diff --git a/src/img/addadmin-command.webp b/src/img/addadmin-command.webp
deleted file mode 100644
index 294d59c..0000000
Binary files a/src/img/addadmin-command.webp and /dev/null differ
diff --git a/src/img/archive_message.webp b/src/img/archive_message.webp
deleted file mode 100644
index 249544e..0000000
Binary files a/src/img/archive_message.webp and /dev/null differ
diff --git a/src/img/auto_setup.webp b/src/img/auto_setup.webp
deleted file mode 100644
index 7684902..0000000
Binary files a/src/img/auto_setup.webp and /dev/null differ
diff --git a/src/img/awaiting_response.webp b/src/img/awaiting_response.webp
deleted file mode 100644
index 5ee3095..0000000
Binary files a/src/img/awaiting_response.webp and /dev/null differ
diff --git a/src/img/blacklist_card.webp b/src/img/blacklist_card.webp
deleted file mode 100644
index 82ce033..0000000
Binary files a/src/img/blacklist_card.webp and /dev/null differ
diff --git a/src/img/blacklist_role_card.webp b/src/img/blacklist_role_card.webp
deleted file mode 100644
index 8856a64..0000000
Binary files a/src/img/blacklist_role_card.webp and /dev/null differ
diff --git a/src/img/blacklist_user_card.webp b/src/img/blacklist_user_card.webp
deleted file mode 100644
index d31f5d4..0000000
Binary files a/src/img/blacklist_user_card.webp and /dev/null differ
diff --git a/src/img/blacklist_user_modal.webp b/src/img/blacklist_user_modal.webp
deleted file mode 100644
index 9bcd9b5..0000000
Binary files a/src/img/blacklist_user_modal.webp and /dev/null differ
diff --git a/src/img/blacklist_user_selection.webp b/src/img/blacklist_user_selection.webp
deleted file mode 100644
index ce25080..0000000
Binary files a/src/img/blacklist_user_selection.webp and /dev/null differ
diff --git a/src/img/blacklist_user_success.webp b/src/img/blacklist_user_success.webp
deleted file mode 100644
index 090a7ec..0000000
Binary files a/src/img/blacklist_user_success.webp and /dev/null differ
diff --git a/src/img/channels.webp b/src/img/channels.webp
deleted file mode 100644
index 331e240..0000000
Binary files a/src/img/channels.webp and /dev/null differ
diff --git a/src/img/close_request.webp b/src/img/close_request.webp
deleted file mode 100644
index 71c92cb..0000000
Binary files a/src/img/close_request.webp and /dev/null differ
diff --git a/src/img/close_request_deny.webp b/src/img/close_request_deny.webp
deleted file mode 100644
index 98d3b9c..0000000
Binary files a/src/img/close_request_deny.webp and /dev/null differ
diff --git a/src/img/close_request_params.webp b/src/img/close_request_params.webp
deleted file mode 100644
index 83f1f2b..0000000
Binary files a/src/img/close_request_params.webp and /dev/null differ
diff --git a/src/img/colour_picker.webp b/src/img/colour_picker.webp
deleted file mode 100644
index 9618a50..0000000
Binary files a/src/img/colour_picker.webp and /dev/null differ
diff --git a/src/img/context_menu_add_sender.webp b/src/img/context_menu_add_sender.webp
deleted file mode 100644
index 077edd3..0000000
Binary files a/src/img/context_menu_add_sender.webp and /dev/null differ
diff --git a/src/img/context_menu_panel.webp b/src/img/context_menu_panel.webp
deleted file mode 100644
index 21c8175..0000000
Binary files a/src/img/context_menu_panel.webp and /dev/null differ
diff --git a/src/img/context_menu_permission_level.webp b/src/img/context_menu_permission_level.webp
deleted file mode 100644
index 9809d71..0000000
Binary files a/src/img/context_menu_permission_level.webp and /dev/null differ
diff --git a/src/img/context_menu_quote_message.webp b/src/img/context_menu_quote_message.webp
deleted file mode 100644
index 7eb263b..0000000
Binary files a/src/img/context_menu_quote_message.webp and /dev/null differ
diff --git a/src/img/context_menu_start_ticket.webp b/src/img/context_menu_start_ticket.webp
deleted file mode 100644
index 5bf7bdd..0000000
Binary files a/src/img/context_menu_start_ticket.webp and /dev/null differ
diff --git a/src/img/dashboard-no-permission.webp b/src/img/dashboard-no-permission.webp
deleted file mode 100644
index a4b1445..0000000
Binary files a/src/img/dashboard-no-permission.webp and /dev/null differ
diff --git a/src/img/developer_mode.webp b/src/img/developer_mode.webp
deleted file mode 100644
index adf4b9b..0000000
Binary files a/src/img/developer_mode.webp and /dev/null differ
diff --git a/src/img/edit_channel.webp b/src/img/edit_channel.webp
deleted file mode 100644
index 7d40831..0000000
Binary files a/src/img/edit_channel.webp and /dev/null differ
diff --git a/src/img/ez_complete.webp b/src/img/ez_complete.webp
deleted file mode 100644
index ff32ad5..0000000
Binary files a/src/img/ez_complete.webp and /dev/null differ
diff --git a/src/img/ez_prefix.webp b/src/img/ez_prefix.webp
deleted file mode 100644
index 67fba7b..0000000
Binary files a/src/img/ez_prefix.webp and /dev/null differ
diff --git a/src/img/feedback_enable.webp b/src/img/feedback_enable.webp
deleted file mode 100644
index aa7787b..0000000
Binary files a/src/img/feedback_enable.webp and /dev/null differ
diff --git a/src/img/feedback_example.webp b/src/img/feedback_example.webp
deleted file mode 100644
index 2bfae3c..0000000
Binary files a/src/img/feedback_example.webp and /dev/null differ
diff --git a/src/img/feedback_stats.webp b/src/img/feedback_stats.webp
deleted file mode 100644
index f32bc76..0000000
Binary files a/src/img/feedback_stats.webp and /dev/null differ
diff --git a/src/img/feedback_transcripts.webp b/src/img/feedback_transcripts.webp
deleted file mode 100644
index 4f91c15..0000000
Binary files a/src/img/feedback_transcripts.webp and /dev/null differ
diff --git a/src/img/feedback_user.webp b/src/img/feedback_user.webp
deleted file mode 100644
index 111990a..0000000
Binary files a/src/img/feedback_user.webp and /dev/null differ
diff --git a/src/img/forms/assignment.webp b/src/img/forms/assignment.webp
deleted file mode 100644
index 1a01040..0000000
Binary files a/src/img/forms/assignment.webp and /dev/null differ
diff --git a/src/img/forms/create.webp b/src/img/forms/create.webp
deleted file mode 100644
index bfe3ccb..0000000
Binary files a/src/img/forms/create.webp and /dev/null differ
diff --git a/src/img/forms/example.webp b/src/img/forms/example.webp
deleted file mode 100644
index 835a7af..0000000
Binary files a/src/img/forms/example.webp and /dev/null differ
diff --git a/src/img/forms/forms_navbar.webp b/src/img/forms/forms_navbar.webp
deleted file mode 100644
index b87d8c1..0000000
Binary files a/src/img/forms/forms_navbar.webp and /dev/null differ
diff --git a/src/img/forms/inputs.webp b/src/img/forms/inputs.webp
deleted file mode 100644
index b26c3ee..0000000
Binary files a/src/img/forms/inputs.webp and /dev/null differ
diff --git a/src/img/forms/output.webp b/src/img/forms/output.webp
deleted file mode 100644
index d2d2f6f..0000000
Binary files a/src/img/forms/output.webp and /dev/null differ
diff --git a/src/img/gdpr/gdpr_confirm.png b/src/img/gdpr/gdpr_confirm.png
deleted file mode 100644
index 0fd4b40..0000000
Binary files a/src/img/gdpr/gdpr_confirm.png and /dev/null differ
diff --git a/src/img/gdpr/gdpr_done.png b/src/img/gdpr/gdpr_done.png
deleted file mode 100644
index 47fd59a..0000000
Binary files a/src/img/gdpr/gdpr_done.png and /dev/null differ
diff --git a/src/img/gdpr/gdpr_messages_confirm.png b/src/img/gdpr/gdpr_messages_confirm.png
deleted file mode 100644
index 07c43ad..0000000
Binary files a/src/img/gdpr/gdpr_messages_confirm.png and /dev/null differ
diff --git a/src/img/gdpr/gdpr_queued.png b/src/img/gdpr/gdpr_queued.png
deleted file mode 100644
index 36cce57..0000000
Binary files a/src/img/gdpr/gdpr_queued.png and /dev/null differ
diff --git a/src/img/gdpr/gdpr_request.png b/src/img/gdpr/gdpr_request.png
deleted file mode 100644
index 7c54ebe..0000000
Binary files a/src/img/gdpr/gdpr_request.png and /dev/null differ
diff --git a/src/img/grant_send_messages_in_thread.webp b/src/img/grant_send_messages_in_thread.webp
deleted file mode 100644
index 5b442af..0000000
Binary files a/src/img/grant_send_messages_in_thread.webp and /dev/null differ
diff --git a/src/img/integrations/edit_welcome_message.webp b/src/img/integrations/edit_welcome_message.webp
deleted file mode 100644
index f298cd6..0000000
Binary files a/src/img/integrations/edit_welcome_message.webp and /dev/null differ
diff --git a/src/img/integrations/example_embed.webp b/src/img/integrations/example_embed.webp
deleted file mode 100644
index bbe300c..0000000
Binary files a/src/img/integrations/example_embed.webp and /dev/null differ
diff --git a/src/img/integrations/example_success.webp b/src/img/integrations/example_success.webp
deleted file mode 100644
index 864ea6d..0000000
Binary files a/src/img/integrations/example_success.webp and /dev/null differ
diff --git a/src/img/integrations/fivem/add_to_server.webp b/src/img/integrations/fivem/add_to_server.webp
deleted file mode 100644
index 016d419..0000000
Binary files a/src/img/integrations/fivem/add_to_server.webp and /dev/null differ
diff --git a/src/img/integrations/fivem/integrations_page.webp b/src/img/integrations/fivem/integrations_page.webp
deleted file mode 100644
index 31731c7..0000000
Binary files a/src/img/integrations/fivem/integrations_page.webp and /dev/null differ
diff --git a/src/img/integrations/fivem/placeholders.webp b/src/img/integrations/fivem/placeholders.webp
deleted file mode 100644
index 4131076..0000000
Binary files a/src/img/integrations/fivem/placeholders.webp and /dev/null differ
diff --git a/src/img/integrations/fivem/welcome_message.webp b/src/img/integrations/fivem/welcome_message.webp
deleted file mode 100644
index 76ce567..0000000
Binary files a/src/img/integrations/fivem/welcome_message.webp and /dev/null differ
diff --git a/src/img/integrations/headers.webp b/src/img/integrations/headers.webp
deleted file mode 100644
index 72b543b..0000000
Binary files a/src/img/integrations/headers.webp and /dev/null differ
diff --git a/src/img/integrations/integration_preview.webp b/src/img/integrations/integration_preview.webp
deleted file mode 100644
index 7b5bad9..0000000
Binary files a/src/img/integrations/integration_preview.webp and /dev/null differ
diff --git a/src/img/integrations/metadata.webp b/src/img/integrations/metadata.webp
deleted file mode 100644
index 6da298d..0000000
Binary files a/src/img/integrations/metadata.webp and /dev/null differ
diff --git a/src/img/integrations/navbar.webp b/src/img/integrations/navbar.webp
deleted file mode 100644
index 83a0ec5..0000000
Binary files a/src/img/integrations/navbar.webp and /dev/null differ
diff --git a/src/img/integrations/placeholder_creation.webp b/src/img/integrations/placeholder_creation.webp
deleted file mode 100644
index a509cc5..0000000
Binary files a/src/img/integrations/placeholder_creation.webp and /dev/null differ
diff --git a/src/img/integrations/request_completed.webp b/src/img/integrations/request_completed.webp
deleted file mode 100644
index 5eb6015..0000000
Binary files a/src/img/integrations/request_completed.webp and /dev/null differ
diff --git a/src/img/integrations/request_url.webp b/src/img/integrations/request_url.webp
deleted file mode 100644
index 4e80cae..0000000
Binary files a/src/img/integrations/request_url.webp and /dev/null differ
diff --git a/src/img/integrations/secrets_example.webp b/src/img/integrations/secrets_example.webp
deleted file mode 100644
index a919d60..0000000
Binary files a/src/img/integrations/secrets_example.webp and /dev/null differ
diff --git a/src/img/invite-1.webp b/src/img/invite-1.webp
deleted file mode 100644
index 140b932..0000000
Binary files a/src/img/invite-1.webp and /dev/null differ
diff --git a/src/img/invite-2.webp b/src/img/invite-2.webp
deleted file mode 100644
index 8949473..0000000
Binary files a/src/img/invite-2.webp and /dev/null differ
diff --git a/src/img/languages.webp b/src/img/languages.webp
deleted file mode 100644
index c02d99d..0000000
Binary files a/src/img/languages.webp and /dev/null differ
diff --git a/src/img/login.webp b/src/img/login.webp
deleted file mode 100644
index 06e0b33..0000000
Binary files a/src/img/login.webp and /dev/null differ
diff --git a/src/img/multi_panel_category.webp b/src/img/multi_panel_category.webp
deleted file mode 100644
index 8729edc..0000000
Binary files a/src/img/multi_panel_category.webp and /dev/null differ
diff --git a/src/img/multipanel_card.webp b/src/img/multipanel_card.webp
deleted file mode 100644
index 41bee3b..0000000
Binary files a/src/img/multipanel_card.webp and /dev/null differ
diff --git a/src/img/multipanel_edit.webp b/src/img/multipanel_edit.webp
deleted file mode 100644
index baf4091..0000000
Binary files a/src/img/multipanel_edit.webp and /dev/null differ
diff --git a/src/img/multipanel_edit_modal.webp b/src/img/multipanel_edit_modal.webp
deleted file mode 100644
index cbf856f..0000000
Binary files a/src/img/multipanel_edit_modal.webp and /dev/null differ
diff --git a/src/img/multipanel_example.webp b/src/img/multipanel_example.webp
deleted file mode 100644
index d930b22..0000000
Binary files a/src/img/multipanel_example.webp and /dev/null differ
diff --git a/src/img/navbar_teams.webp b/src/img/navbar_teams.webp
deleted file mode 100644
index 6b34989..0000000
Binary files a/src/img/navbar_teams.webp and /dev/null differ
diff --git a/src/img/panel_card.webp b/src/img/panel_card.webp
deleted file mode 100644
index ea9bad8..0000000
Binary files a/src/img/panel_card.webp and /dev/null differ
diff --git a/src/img/panel_edit.webp b/src/img/panel_edit.webp
deleted file mode 100644
index bb95815..0000000
Binary files a/src/img/panel_edit.webp and /dev/null differ
diff --git a/src/img/panel_success.webp b/src/img/panel_success.webp
deleted file mode 100644
index e13d377..0000000
Binary files a/src/img/panel_success.webp and /dev/null differ
diff --git a/src/img/panels_navbar.webp b/src/img/panels_navbar.webp
deleted file mode 100644
index a67d5db..0000000
Binary files a/src/img/panels_navbar.webp and /dev/null differ
diff --git a/src/img/panels_page.webp b/src/img/panels_page.webp
deleted file mode 100644
index da72f46..0000000
Binary files a/src/img/panels_page.webp and /dev/null differ
diff --git a/src/img/server_language.webp b/src/img/server_language.webp
deleted file mode 100644
index d4b6e35..0000000
Binary files a/src/img/server_language.webp and /dev/null differ
diff --git a/src/img/server_list.webp b/src/img/server_list.webp
deleted file mode 100644
index 91a93bf..0000000
Binary files a/src/img/server_list.webp and /dev/null differ
diff --git a/src/img/settings_card.webp b/src/img/settings_card.webp
deleted file mode 100644
index 007c67d..0000000
Binary files a/src/img/settings_card.webp and /dev/null differ
diff --git a/src/img/settings_claim.webp b/src/img/settings_claim.webp
deleted file mode 100644
index 67801cf..0000000
Binary files a/src/img/settings_claim.webp and /dev/null differ
diff --git a/src/img/setup_command.webp b/src/img/setup_command.webp
deleted file mode 100644
index c0c7130..0000000
Binary files a/src/img/setup_command.webp and /dev/null differ
diff --git a/src/img/slash_commands.webp b/src/img/slash_commands.webp
deleted file mode 100644
index dfbdad7..0000000
Binary files a/src/img/slash_commands.webp and /dev/null differ
diff --git a/src/img/staff_teams_card.webp b/src/img/staff_teams_card.webp
deleted file mode 100644
index 957e949..0000000
Binary files a/src/img/staff_teams_card.webp and /dev/null differ
diff --git a/src/img/staff_teams_delete.webp b/src/img/staff_teams_delete.webp
deleted file mode 100644
index 22abdae..0000000
Binary files a/src/img/staff_teams_delete.webp and /dev/null differ
diff --git a/src/img/staff_teams_manage.webp b/src/img/staff_teams_manage.webp
deleted file mode 100644
index 78257c2..0000000
Binary files a/src/img/staff_teams_manage.webp and /dev/null differ
diff --git a/src/img/tags_card_example.webp b/src/img/tags_card_example.webp
deleted file mode 100644
index 1712f5e..0000000
Binary files a/src/img/tags_card_example.webp and /dev/null differ
diff --git a/src/img/tags_editor_advanced.webp b/src/img/tags_editor_advanced.webp
deleted file mode 100644
index 1253390..0000000
Binary files a/src/img/tags_editor_advanced.webp and /dev/null differ
diff --git a/src/img/tags_editor_basic.webp b/src/img/tags_editor_basic.webp
deleted file mode 100644
index ad490bb..0000000
Binary files a/src/img/tags_editor_basic.webp and /dev/null differ
diff --git a/src/img/tags_id_example.webp b/src/img/tags_id_example.webp
deleted file mode 100644
index 71b1743..0000000
Binary files a/src/img/tags_id_example.webp and /dev/null differ
diff --git a/src/img/tags_message_example.webp b/src/img/tags_message_example.webp
deleted file mode 100644
index 24b7339..0000000
Binary files a/src/img/tags_message_example.webp and /dev/null differ
diff --git a/src/img/tags_message_full_example.webp b/src/img/tags_message_full_example.webp
deleted file mode 100644
index b4b628b..0000000
Binary files a/src/img/tags_message_full_example.webp and /dev/null differ
diff --git a/src/img/tags_message_inline.webp b/src/img/tags_message_inline.webp
deleted file mode 100644
index 00398b0..0000000
Binary files a/src/img/tags_message_inline.webp and /dev/null differ
diff --git a/src/img/threads_command.webp b/src/img/threads_command.webp
deleted file mode 100644
index 469093b..0000000
Binary files a/src/img/threads_command.webp and /dev/null differ
diff --git a/src/img/threads_enable_dashboard.webp b/src/img/threads_enable_dashboard.webp
deleted file mode 100644
index dc20915..0000000
Binary files a/src/img/threads_enable_dashboard.webp and /dev/null differ
diff --git a/src/img/ticket_close_confirmation.webp b/src/img/ticket_close_confirmation.webp
deleted file mode 100644
index fb4e0e0..0000000
Binary files a/src/img/ticket_close_confirmation.webp and /dev/null differ
diff --git a/src/img/ticket_notification.webp b/src/img/ticket_notification.webp
deleted file mode 100644
index e45c7c5..0000000
Binary files a/src/img/ticket_notification.webp and /dev/null differ
diff --git a/src/img/tickets_card.webp b/src/img/tickets_card.webp
deleted file mode 100644
index d052198..0000000
Binary files a/src/img/tickets_card.webp and /dev/null differ
diff --git a/src/img/tickets_docs_readme_usage.webp b/src/img/tickets_docs_readme_usage.webp
deleted file mode 100644
index a1f1684..0000000
Binary files a/src/img/tickets_docs_readme_usage.webp and /dev/null differ
diff --git a/src/img/tickets_view_compare.webp b/src/img/tickets_view_compare.webp
deleted file mode 100644
index bdf2183..0000000
Binary files a/src/img/tickets_view_compare.webp and /dev/null differ
diff --git a/src/img/transcripts_card.webp b/src/img/transcripts_card.webp
deleted file mode 100644
index acfeb60..0000000
Binary files a/src/img/transcripts_card.webp and /dev/null differ
diff --git a/src/img/video_thumbnails/Thumbnail_Forms.webp b/src/img/video_thumbnails/Thumbnail_Forms.webp
deleted file mode 100644
index 9b82d1e..0000000
Binary files a/src/img/video_thumbnails/Thumbnail_Forms.webp and /dev/null differ
diff --git a/src/img/video_thumbnails/Thumbnail_Reaction_Panels.webp b/src/img/video_thumbnails/Thumbnail_Reaction_Panels.webp
deleted file mode 100644
index 3b1cac5..0000000
Binary files a/src/img/video_thumbnails/Thumbnail_Reaction_Panels.webp and /dev/null differ
diff --git a/src/img/video_thumbnails/Thumbnail_Staff_Teams.webp b/src/img/video_thumbnails/Thumbnail_Staff_Teams.webp
deleted file mode 100644
index 3036c8a..0000000
Binary files a/src/img/video_thumbnails/Thumbnail_Staff_Teams.webp and /dev/null differ
diff --git a/src/img/welcome_message.webp b/src/img/welcome_message.webp
deleted file mode 100644
index ac8b06e..0000000
Binary files a/src/img/welcome_message.webp and /dev/null differ
diff --git a/src/img/whitelabel/activate_premium.webp b/src/img/whitelabel/activate_premium.webp
deleted file mode 100644
index 19972d5..0000000
Binary files a/src/img/whitelabel/activate_premium.webp and /dev/null differ
diff --git a/src/img/whitelabel/copy_token.webp b/src/img/whitelabel/copy_token.webp
deleted file mode 100644
index c4002d9..0000000
Binary files a/src/img/whitelabel/copy_token.webp and /dev/null differ
diff --git a/src/img/whitelabel/custom_status.webp b/src/img/whitelabel/custom_status.webp
deleted file mode 100644
index 4fbad67..0000000
Binary files a/src/img/whitelabel/custom_status.webp and /dev/null differ
diff --git a/src/img/whitelabel/general_information.webp b/src/img/whitelabel/general_information.webp
deleted file mode 100644
index 6a41564..0000000
Binary files a/src/img/whitelabel/general_information.webp and /dev/null differ
diff --git a/src/img/whitelabel/invite.webp b/src/img/whitelabel/invite.webp
deleted file mode 100644
index 4e07715..0000000
Binary files a/src/img/whitelabel/invite.webp and /dev/null differ
diff --git a/src/img/whitelabel/kick_bot.webp b/src/img/whitelabel/kick_bot.webp
deleted file mode 100644
index 248ebdb..0000000
Binary files a/src/img/whitelabel/kick_bot.webp and /dev/null differ
diff --git a/src/img/whitelabel/new_application.webp b/src/img/whitelabel/new_application.webp
deleted file mode 100644
index a58e529..0000000
Binary files a/src/img/whitelabel/new_application.webp and /dev/null differ
diff --git a/src/img/whitelabel/policies.webp b/src/img/whitelabel/policies.webp
deleted file mode 100644
index 52cba4a..0000000
Binary files a/src/img/whitelabel/policies.webp and /dev/null differ
diff --git a/src/img/whitelabel/submit_token.webp b/src/img/whitelabel/submit_token.webp
deleted file mode 100644
index 2877dbb..0000000
Binary files a/src/img/whitelabel/submit_token.webp and /dev/null differ
diff --git a/src/integrations/building-integrations.md b/src/integrations/building-integrations.md
deleted file mode 100644
index 288cea2..0000000
--- a/src/integrations/building-integrations.md
+++ /dev/null
@@ -1,222 +0,0 @@
-# Build Integrations
-
-Integrations let you include information retrieved from your own web server, or 3rd party APIs, directly in the welcome messages of your tickets!
-
-In this guide, we'll build an integration from scratch together, from start to finish.
-
-## What can I use integrations for?
-If you run a service that incorporates [Discord OAuth](https://discord.com/developers/docs/topics/oauth2), you have a use case for integrations! Since your user objects are linked to Discord accounts, you can expose an API endpoint that Tickets can request to include information about the user in the ticket.
-
-A simple example would be a forum! When a user opens a ticket in your Discord server, you could include the user's forum username automatically.
-
-Integrations do not necessarily need to fetch information about a user either! In the [next tutorial](), we show you how we built the cryptocurrency price integration.
-
-## Background Setup
-Let's say we run a game, where users link their accounts to their Discord accounts. Users have usernames, scores and other metadata which we wish to display in the welcome message when a user opens a ticket.
-
-The following is some simple code that serves some example JSON data that we will be using for this tutorial. Let's say that this code is running on a web server, accessible at `https://example.tickets.bot`:
-
-```js
-const express = require("express");
-const app = express();
-
-let users = {
- "585576154958921739": {
- online_status: "Online",
- user: {
- username: "Ryan",
- account_created_year: 2019,
- scores: {
- high_score: 3000,
- last_score: 400,
- },
- },
- },
-};
-
-app.get("/lookup", (req, res) => res.json(users[req.query.user] || {}));
-
-app.listen(process.env.PORT, () => console.log("Listening..."));
-```
-
-The server responds with the user object stored in the `users` dictionary if it exists, or alternatively with an empty JSON object, `{}`.
-
-For example, sending a request to `https://example.tickets.bot/lookup?user=585576154958921739`:
-
-```bash
-$ curl https://example.tickets.bot/lookup?user=585576154958921739 | jq .
-{
- "online_status": "Online",
- "user": {
- "username": "Ryan",
- "account_created_year": 2019,
- "scores": {
- "high_score": 3000,
- "last_score": 400
- }
- }
-}
-```
-
-Your integration **MUST** return a JSON response. Parsing other data formats is not supported. You may return the data structured in any way you want, as long as it is valid JSON.
-
-All data types are supported, except for JSON arrays. You should pre-process your arrays and join them to strings.
-
-## Creating Your Integration
-Now that we have somewhere to pull data from, we can start linking it up with Tickets!
-
-First, head over to our [web dashboard](https://dashboard.tickets.bot), select any server, and then navigate to the Integrations tab in the navbar. From there, you will be able to press the "Create Integration" button:
-
-
-
-Then, fill out some basic information about your integration: its name, description, and optionally logo image URL and privacy policy. It is recommended to set a privacy policy if you are creating a public integration. You will be able to see a preview on the right-hand side as you type. Once completed, press the "Continue" button.
-
-
-
-### HTTP Request
-
-You will be then be prompted to enter information about how the integration works. Lets focus on the "HTTP Request" section first:
-
-
-
-Upon a ticket being opened, we will send a HTTP request to the provided request URL, to which you should respond with a JSON object that we can extract values of your choice from. You can use the placeholder `%user_id%` in the URL, which will be replaced with the user ID of the user who opened the ticket. In our case, we set this to `https://example.tickets.bot/lookup?user=%user_id%`.
-
-Requests can either be sent as GET or POST requests. POST requests are sent with a JSON body with information about the ticket. An example body is as follows:
-
-```json
-{
- "guild_id": "508392876359680000",
- "user_id": "508391840525975553",
- "ticket_id": 30,
- "ticket_channel_id": "508392988985262090",
- "is_new_ticket": true,
- "form_data": {
- "What is your question?": "I have a problem with XYZ",
- "What is your email address?": "user@example.com"
- }
-}
-```
-
-The `is_new_ticket` denotes whether the request is being made due to a new ticket being created. Placeholders are supported in tags and other places, in which case `is_new_ticket` would be `false`.
-
-The `form_data` field is only included for **private** integrations. There is no reason for public integrations to include form data, as forms are specific to the server.
-
-### Headers and Secrets
-It is recommended that you add some kind of authentication to your API- or if you are making an integration that requests a public API, you will definitely be required to use authentication. Thankfully, you can add HTTP headers to your integration requests!
-
-Let's say our example app now requires an API key to be sent in the `Authorization` header. Simply press the `Add Additional Header` button, and enter the header name and value, like so:
-
-
-
-This functionality can be further extended by using secrets: You can ask users to supply their _own_ secret values, such as API keys, when adding your integration to their server. For example, we may want users to register an application on our own site, generate them an API key, and make them input it when adding your integration. Let's take a look at an example:
-
-
-
-We have created a secret, called `api_key`, which we are able to use in either headers, or the URL itself, via `%api_key%`. When a user adds your integration to their server, they will be prompted to enter their API key:
-
-
-
-### Secret Validation
-Sometimes, users may provide a secret value in an invalid format, or otherwise incorrect way. You may optionally define a validation URL that we will send an HTTP POST to every time a user adds your integration to a server to dynamically validate their secrets. The request will contain a JSON body containing the user's secret values:
-```json
-{
- "secret_name": "value",
- "secret2_name": "abcde"
-}
-```
-
-If the values satisfy your constraints, simply respond with any 2XX status code. The response body does not matter, so it is recommended to use HTTP 204 No Content with an empty body.
-
-If the value does not satisfy your constraints, then respond with any non-2XX status code - HTTP 400 Bad Request is well suited. You may also provide a JSON response body with a single "error" field containing a message to show to the user:
-```json
-{
- "error": "Your API key is invalid."
-}
-```
-
-### Placeholders
-Next, we are onto creating the placeholders themselves. Here, you define how each value in your JSON response should be mapped to the variables that can be used in welcome messages.
-
-As a reminder, in our example application, we respond with the following JSON:
-
-```json
-{
- "online_status": "Online",
- "user": {
- "username": "Ryan",
- "account_created_year": 2019,
- "scores": {
- "high_score": 3000,
- "last_score": 400
- }
- }
-}
-```
-
-The JSON path is simply the path of keys to access a value. Nested objects can be accessed by splitting the path with a dot.
-
-For example, the path `online_status` would yield `Online`, and `user.username` would yield `Ryan`.
-
-Let's take a look at how we'd register these with the integration settings:
-
-
-
-It should be obvious to see how the values are mapped. Note, your placeholder itself can be named completely separate from the JSON path.
-
-You have now successfully configured your first integration! All that is left is to press the final "Create" button. After doing this, you should be taken to a preview page for your integration:
-
-
-
-You can view the list of available placeholders on the right-hand side of the page. Don't forget to _activate_ the integration in your server, by pressing the "Add to server" button!
-
-## Using Placeholders
-Now that we have created out integration and added it to our server (don't forget this part), we can implement the placeholders!
-
-You'll need to head over to the "Ticket Panels" tab of the dashboard for your server, press edit on a panel, and open the welcome message editor:
-
-
-
-We can then insert our placeholders into the welcome message, like so:
-
-
-
-Let's test it out!
-
-
-
-As you can see, the placeholders have successfully been fetched from the web server, and replaced with the provided values!
-
-## Need Help?
-If you're still stuck, feel free to ask us in our [Discord server](https://discord.gg/ticketsbot)!
-
-## Security
-We have put **significant** effort into making sure integrations are safe, by ensuring requests are always proxied, and not sent to where they are not supposed to be, including through additional penetration testing.
-
-Integration HTTP requests should be sent to your server via AS13335 (Cloudflare), and it should not be possible to send a request to a private IP.
-
-
-
-
-Regarding integrations, we are particularly interested in vulnerabilities related to:
-
-- Accessing internal services
-- Exposing the origin IPs of our nodes
-- Accessing secret values of other servers
-- Accessing the IP address of another user, via viewing integration logos
-
-Integration logos are proxied by dedicated images proxy nodes running on AS16276 (OVH). These nodes are located outside of our internal network, and do not serve any other purpose. We are not concerned with hiding the IP addresses of these nodes. Note that integration logos viewed on the integration creation and updating pages are _not_ proxied, as they are only viewable by the integration creator, and so would be classed as a self-attack.
-
-When performing security research, please:
-
-- Ensure that target assets are in-scope and operated by us (we utilise serverless functions on infrastructure not run by us). If you are unsure, open a ticket and ask.
-- Do not use automated scanners
-- Do not launch (D)DoS / resource exhaustion attacks
-
-If you wish to perform static code analysis for your research, you can view the relevant open source code here:
-
-- Integration Proxy
- - [secure-proxy](https://github.com/TicketsBot-cloud/tickets.rs/tree/master/secure-proxy)
- - [global-resolver](https://github.com/TicketsBot-cloud/tickets.rs/tree/master/global-resolver)
-- Image Proxy
- - [image-proxy](https://github.com/TicketsBot-cloud/tickets.rs/tree/master/image-proxy)
- - [global-resolver](https://github.com/TicketsBot-cloud/tickets.rs/tree/master/global-resolver)
diff --git a/src/integrations/cloudflare-workers.md b/src/integrations/cloudflare-workers.md
deleted file mode 100644
index 7bdba21..0000000
--- a/src/integrations/cloudflare-workers.md
+++ /dev/null
@@ -1,54 +0,0 @@
-# Using Cloudflare Workers
-Sometimes services return data in a slightly different format than you want. Since Tickets integrations are only capable of reading exact JSON keys, some additional processing may be required.
-
-For example, FiveM servers return data in the following format, which posed an issue when creating our FiveM integration:
-```json
-{
- ...
- "Data": {
- ...
- "players": [
- ...,
- {
- "id": 100,
- "identifiers": ["discord:111111111111111111", "license:abcdefg"],
- "name": "Username",
- },
- ...
- ]
- }
-}
-```
-
-We are given a list of all players on the server, which we must search to find the player with the identifier `discord:%user_id%`.
-
-Cloudflare Workers come in here.
-
-## What are Cloudflare Workers
-[Cloudflare Workers](https://workers.cloudflare.com/) allow you to deploy serverless code (including JavaScript, and more), for free, with the click of a button. We can write a worker to listen to requests from Tickets, query the service we are integrating with, process the data, and return it to Tickets in an easy to read format.
-
-Looking at the FiveM integration again, the integration sends a request to `https://worker-name.xxxx.workers.dev/?serverid=%server_id%&user_id=%user_id`. The worker extracts the server ID and user ID from the URL, and then sends a request to the FiveM API with the provided server ID. It then parses the response, finds the user object, and responds with a simple JSON object:
-```json
-{
- "username": "Username",
- "steam_id": 123456,
- "steam_url": "https://steamcommunity.com/profiles/123456",
- ...
-}
-```
-
-If you want users to be able to include a URL in their welcome messages (e.g. Steam profile URL), a neat trick is to return the full URL as a placeholder, rather than making users construct it themselves in their welcome messages using just the Steam ID.
-
-If you are serving data that does not frequently change, you can use the workers [Key-Value Storage API](https://developers.cloudflare.com/workers/learning/how-kv-works/) to cache data, to reduce CPU time used.
-
-The full Cloudflare worker documentation is available [here](https://developers.cloudflare.com/workers/).
-
-## Security
-You should add an Authorization header to your requests, so that malicious people are not able to send extraneous requests to your worker. An example code snippet is as follows:
-
-```js
-let authHeader = request.headers.get("Authorization");
-if (!authHeader || authHeader !== AUTH_SECRET) {
- return respondWithCode(401, {error: "Invalid auth key"});
-}
-```
diff --git a/src/integrations/fivem.md b/src/integrations/fivem.md
deleted file mode 100644
index 1620c58..0000000
--- a/src/integrations/fivem.md
+++ /dev/null
@@ -1,32 +0,0 @@
-# Using the FiveM Integration
-If you run a FiveM server, you can use our FiveM integration to fetch the FiveM IDs, usernames, Steam IDs and more of users who open tickets in your server!
-
-To activate the FiveM integration in your server, head over to our [web dashboard](https://dashboard.tickets.bot) and select your Discord server. Then, select the "Integrations" tab in the navbar, find the FiveM integration, and press "Add to server":
-
-
-
-You will then be prompted for your *FiveM* server ID. This is the 6 character alphanumeric string assigned to your server. If you do not know it, you can find it on [KeyMaster](https://keymaster.fivem.net/), or in the FiveM server list.
-
-
-
-The integration is now active in your server! The last step is to insert the placeholders of your choice into the ticket welcome message. To do this, head over to the "Ticket Panels" page, press "Edit" on a ticket panel, expand advanced settings, and open the welcome message editor:
-
-
-Then, customise the welcome message to your liking:
-
-
-The placeholders provided by the FiveM integration are:
-- %fivem_id%
-- %fivem_username%
-- %steam_id%
-- %steam_profile_url%
-- %fivem_license%
-- %fivem_license2%
-
-Finally, test it out by opening a ticket:
-
-
-## Limitations
-- The user opening the ticket must be connected to your FiveM server at the time
-- It is possible to not have a Steam account linked to a FiveM account
-- It is possible to not have a Discord account linked to a FiveM account, meaning the integration will be unable to retrieve the data
diff --git a/src/integrations/introduction.md b/src/integrations/introduction.md
deleted file mode 100644
index 0dbc619..0000000
--- a/src/integrations/introduction.md
+++ /dev/null
@@ -1,4 +0,0 @@
-# Integrations
-This chapter provides information regarding integrations, and how to build them.
-
-Use the sidebar to navigate this chapter.
\ No newline at end of file
diff --git a/src/introduction/introduction.md b/src/introduction/introduction.md
deleted file mode 100644
index 98aa2a0..0000000
--- a/src/introduction/introduction.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# Tickets V2 Bot Official Documentation
-
-These Docs will help you with:
-* Setting up the Bot
-* Explain each feature of the Bot
-* Tell you how to set each feature up
-* How to use the bot correctly
-* How to fix issues with permissions
-
-## These Docs are a living Document
-Updates to the docs are made frequently.
-
-
-
-**If you find any issues in the Docs like typo's and outdated information then please tell us in our [support server](https://discord.gg/ticketsbot).**
-
-
-Get started setting up the bot [here](../setup/introduction.md)
diff --git a/src/miscellaneous/dashboard-no-permission.md b/src/miscellaneous/dashboard-no-permission.md
deleted file mode 100644
index b8129fa..0000000
--- a/src/miscellaneous/dashboard-no-permission.md
+++ /dev/null
@@ -1,10 +0,0 @@
-# Dashboard: "No Permission" Message
-When the bot is first added to the server, you may receive a "No Permission" warning on the dashboard when trying to manage it.
-
-
-
-This is because Tickets uses its own permission management system, and ignores any permissions you may have in the Discord server itself.
-
-In order to gain access to the web dashboard for your server, ask the **server owner** to add you as a bot admin using the `/addadmin @User` command. You can read more about the `/addadmin` command in [the command guide](../commands/add-admin-support.md).
-
-
diff --git a/src/miscellaneous/introduction.md b/src/miscellaneous/introduction.md
deleted file mode 100644
index c6a3944..0000000
--- a/src/miscellaneous/introduction.md
+++ /dev/null
@@ -1,4 +0,0 @@
-# Miscellaneous
-This chapter contains all other documents which do not suit the other chapters.
-
-Use the sidebar to navigate this chapter.
\ No newline at end of file
diff --git a/src/miscellaneous/official-links.md b/src/miscellaneous/official-links.md
deleted file mode 100644
index ad0e387..0000000
--- a/src/miscellaneous/official-links.md
+++ /dev/null
@@ -1,17 +0,0 @@
-# Official Links
-***
-
-### Website
-[tickets.bot](https://tickets.bot/)
-
-### Invite The Bot
-[invite.tickets.bot](https://invite.tickets.bot/)
-
-### Dashboard
-[dashboard.tickets.bot](https://dashboard.tickets.bot/)
-
-### Documentation
-[docs.tickets.bot](https://docs.tickets.bot/)
-
-### Discord Support Server
-[Support Server](https://discord.gg/ticketsbot)
\ No newline at end of file
diff --git a/src/miscellaneous/permissions-explained.md b/src/miscellaneous/permissions-explained.md
deleted file mode 100644
index d24fe05..0000000
--- a/src/miscellaneous/permissions-explained.md
+++ /dev/null
@@ -1,52 +0,0 @@
-# All Bot Permissions Explained
-
-***
-For the bot to work fully it needs many permissions.
-
-Either you manually give it each needed permissions or you give it the `Administrator` permission which will just make it "work". For an explanation of how to adjust permissions, [check the Discord help article](https://support.discord.com/hc/en-us/articles/206029707-How-do-I-set-up-Permissions).
-
-Below is a rough explanation of what each permission is used for:
-
-* `View Channels` "Allows the bot to view the content of a channel."
-
-* `Manage Channels` "Allows the bot to create, rename, recategorize, and delete channels."
-
-* `Manage Roles` "Allows the bot to create and edit roles, give and take away roles from users, and adjust a channel's role permissions."
-
-* `Manage Webhooks` "Allows the bot to create webhooks for transcripts, and for staff to use the dashboard to send messages or tags in open tickets."
-
-* `Send Messages` "Allows the bot to send messages in channels."
-
-* `Send TTS Messages` "Allows the bot to assign this permission to ticket openers and staff members."
-
-* `Send Messages in Threads` "Allows the bot to send messages in threads."
-
-* `Create Public Threads` "Allows the bot to create public threads."
-
-* `Create Private Threads` "Allows the bot to create private threads, such as thread mode tickets and the /notes command for channel tickets."
-
-* `Embed Links` "Allows the bot to send ticket panels, welcome messages, and tags that include an embedded message."
-
-* `Attach Files` "Allows the bot to assign this permission to ticket openers and staff members."
-
-* `Add Reactions` "Allows the bot to add the buttons to ticket panels, welcome messages, and all commands that use buttons."
-
-* `Use External Emojis` "Allows the bot to use non-server emojis in ticket panels, welcome messages, and tags. The bot must still be in the other server to use them."
-
-* `Pin Messages` "Allows the bot to pin the welcome message and its buttons on ticket creation."
-
-* `Mention @Everyone` "Allows the bot to mention everyone, here and all roles in a ticket."
-
-* `Manage Threads` "Allows the bot to create, rename, close, and delete threads."
-
-* `Read Message History` "Allows the bot to read all messages in a channel."
-
-* `Use Application Commands` "Allows the bot's slash commands to work."
-
-* `Use External Stickers` "Allows the bot to assign this permission to ticket openers and staff members."
-
-* `Send Voice Messages` "Allows the bot to assign this permission to ticket openers and staff members."
-
-These permissions are mandatory so that the bot can work. Any other permission can be denied for the bot to use since those aren't used by the bot.
-
-> **Note:** The used permissions can change when the bot gets a new update or feature. Please keep a lookout, for an announcement about changed permissions in our [support server](https://discord.gg/ticketsbot).
diff --git a/src/miscellaneous/placeholders.md b/src/miscellaneous/placeholders.md
deleted file mode 100644
index 6d8997e..0000000
--- a/src/miscellaneous/placeholders.md
+++ /dev/null
@@ -1,82 +0,0 @@
-# Placeholders
-***
-
-## Welcome Message Placeholders
-### Built-in
-
-|Placeholder|Description |
-|--|--|
-| %user% | Mentions the user, will display nickname if set |
-| %username% | Display the user's name |
-| %user_id% | Display the user's numeric ID |
-| %ticket_id% | Display the ticket's numeric ID |
-| %open_tickets% | Display the number of open tickets in the server |
-| %total_tickets% | Display the number of tickets that have ever been opened in the server |
-| %user_open_tickets% | Display the number of tickets that the user currently has open in the server |
-| %user_total_tickets% | Display the number of tickets that the user has ever opened in the server |
-| %ticket_limit% | Display the server's ticket limit |
-| %channel% | Mention the channel |
-| %rating_count% | Amount of feedback ratings you have received |
-| %average_rating% | Displays server's average feedback rating |
-| %time% | Display the current time |
-| %date% | Display today's date |
-| %datetime% | Display the current date and time |
-| %timestamp% | Display the current Unix timestamp as a raw number |
-| %date_days:N% | Display a date N days from now |
-| %date_days:N:FORMAT% | Display a date N days from now with Discord format |
-| %date_weeks:N% | Display a date N weeks from now |
-| %date_weeks:N:FORMAT% | Display a date N weeks from now with Discord format |
-| %date_months:N% | Display a date N months from now |
-| %date_months:N:FORMAT% | Display a date N months from now with Discord format |
-| %date_timestamp:UNIX% | Convert a Unix timestamp to a date |
-| %date_timestamp:UNIX:FORMAT% | Convert a Unix timestamp to a date with Discord format |
-| %timestamp_days:N% | Display the raw Unix timestamp N days from now |
-| * %first_response_time_weekly% | Staff average first response time to tickets this week |
-| * %first_response_time_monthly% | Staff average first response time to tickets this month |
-| * %first_response_time_all_time% | Staff average first response time to tickets since the beginning |
-| %discord_account_creation_date% | The date and time that the user's Discord account was created |
-| %discord_account_age% | How long ago the user's Discord account was created |
-
-Placeholders marked with a * are premium features. Learn more about premium [here](https://tickets.bot/premium).
-
-**N** = number of days/weeks/months
-
-**UNIX** = Unix timestamp
-
-**FORMAT** = Discord format code: `d` (short date), `D` (long date), `t` (short time), `T` (long time), `f` (short date/time, default), `F` (long date/time), `R` (relative)
-
-### Integrations
-All integration placeholders are automatically active, you do not have to do anything special apart from include them in your welcome message.
-
-#### Bloxlink
-> β οΈ **Bloxlink placeholders are currently unavailable.** Bloxlink has disabled their Global API, which these placeholders relied upon. We are investigating alternative solutions to restore Roblox placeholder support, but are unable to provide an estimated timeline.
-
-## Custom Naming Scheme Placeholders:
-|Placeholder|Description|
-|--|--|
-| %id% | Display the unique ticket ID |
-| %id_padded% | Display the unique ticket ID to 4 places |
-| %username% | Display the user's name |
-| %nickname% | Display the user's nickname |
-| %claimed% | Display whether the ticket is claimed or unclaimed |
-| %claim_indicator% | Display π’ if claimed or π΄ if unclaimed |
-| %claimed_by% | Display the claimer's username |
-| %date% | Display the current date in short format |
-| %date:FORMAT% | Display the current date with custom format |
-| %date_days:N% | Display a date N days from now |
-| %date_days:N:FORMAT% | Display a date N days from now with custom format |
-| %date_weeks:N% | Display a date N weeks from now |
-| %date_weeks:N:FORMAT% | Display a date N weeks from now with custom format |
-| %date_months:N% | Display a date N months from now |
-| %date_months:N:FORMAT% | Display a date N months from now with custom format |
-| %date_timestamp:UNIX% | Convert a Unix timestamp to a date |
-| %date_timestamp:UNIX:FORMAT% | Convert a Unix timestamp to a date with custom format |
-
-**N** = number of days/weeks/months
-
-**UNIX** = Unix timestamp
-
-**FORMAT** = custom format using tokens: `yyyy` (4-digit year), `yy` (2-digit year), `mm` (zero-padded month), `m` (single-digit month), `dd` (zero-padded day), `d` (single-digit day). Use any separator, e.g. `yyyy-mm-dd`, `d/m/yy`, `dd.mm.yyyy`. Defaults to short format (`jan19`) if not specified.
-
-## Escaping Placeholders
-To display a placeholder as literal text instead of having it replaced, use backslashes: `\%placeholder\%`
diff --git a/src/premium/introduction.md b/src/premium/introduction.md
deleted file mode 100644
index 365de12..0000000
--- a/src/premium/introduction.md
+++ /dev/null
@@ -1,4 +0,0 @@
-# Premium
-This chapter provides information regarding the premium tiers offered for the bot.
-
-Use the sidebar to navigate this chapter.
diff --git a/src/premium/perks.md b/src/premium/perks.md
deleted file mode 100644
index 140a697..0000000
--- a/src/premium/perks.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# Tier Comparison
-***
-
-| Feature | Free | VotingPremium | Premium | Whitelabel | -|--|--|--|--|--| -| Unlimited Tickets | X | X | X | X | -| Automatic Ticket Archives | X | X | X | X | -| Forms | X | X | X | X | -| Ticket Claiming | X | X | X | X | -| Access Control | X | X | X | X | -| Access to Autoclose | OnΒ Leave | On Leave | X | X | -| Max Ticket Panels | 3 | 3 | Unlimited | Unlimited | -| Panel Support Hours | 1 | 1 | Unlimited | Unlimited | -| Message Branding Removal | - | Welcome Message | X | X | -| Access to Statistics | - | X | X | X | -| Awaiting Response Category | - | - | X | X | -| Exit Surveys | - | - | X | X | -| Customise Embed Colour | - | - | X | X | -| Live Message Updates on the Dashboard | - | - | X | X | -| Send Messages Directly from the Dashboard | - | - | X | X | -| Custom Tag Alias | - | - | X | X | -| Customize Bot Name | - | - | - | X | -| Customize Bot Avatar | - | - | - | X | -| Customize Bot Status | - | - | - | X | diff --git a/src/premium/whitelabel-setup-guide.md b/src/premium/whitelabel-setup-guide.md deleted file mode 100644 index 95ddff0..0000000 --- a/src/premium/whitelabel-setup-guide.md +++ /dev/null @@ -1,96 +0,0 @@ -# Whitelabel Setup Guide -*** - -Thanks for purchasing whitelabel and supporting us! - -Please follow this guide **very carefully**. If you skip a single step, the process will not work. The setup is short, and will only need to be done once. - - -## (Step 1 of 5) Link Patreon Account -If you haven't done so already, you'll need to link your Patreon and Discord accounts on [this page](https://www.patreon.com/settings/apps). - -Patreon has a longer guide on how to do this [here](https://support.patreon.com/hc/en-us/articles/212052266-Get-my-Discord-role). - - -## (Step 2 of 5) Create Bot -Next, you'll need to create your custom bot that Tickets will run under. - -To do this, visit the [Discord developer portal](https://discord.com/developers/applications) and press `New Application` in the top right: - - - -Enter a name for your bot and press create. - -From here, you can change your bot's avatar: - - - - -## (Step 3 of 5) Start Bot -Next, you have to submit the bot's token. This is like a password to the bot. **Never send this token to anyone, even in our support server.** - -Click on `Bot` on the sidebar of the Discord developer portal and copy the token (you may have to click the `reset token` button before you can copy): - - - -Then head over to the Tickets dashboard [Whitelabel section](https://dashboard.tickets.bot/whitelabel). Paste the token into the `Bot Token` field and press `Submit`: - -> **Note:** -> - There may be up to a 10 minute delay for the whitelabel section of dashboard to recognize your status. -> - Until it does, it will lead you back to the "buy premium/whitelabel" page. - - - -You will then be presented with a message saying that the bot is now online. - -If you receive an error, make sure that you copied the token (not the client secret) fully. Additionally, refresh the page and check the `Error Log` table for any errors. - - -## (Step 4 of 5) Invite Bot To Server -Before you can invite the bot to your server, you must kick the main `Tickets v2#5105` bot from your server. It is **extremely** important that you do this **before** inviting your custom bot to your server. If you do not do this, you risk data loss. - - - -To invite your whitelabel bot to your server, click the `Generate Invite Link` button under the Manage Bot section. - -Upon clicking the button, you will be taken to the normal bot invite page - select your server and authorise. It is important that you grant the bot all the permissions that it asks for. - - - - -## (Step 5 of 5) Activate Premium Perks -The last mandatory step is to activate the premium perks that come with whitelabel for your server. - -> **Note:** -> - There may be up to a 10 minute delay for the whitelabel bot to recognize the guild/server and synch commands. -> - Until it does, it will error when running commands. -> - If command errors, wait 10 minutes and try the command again. - -Go to your discord server and run the command `/premium`. You must select the command when it displays to you after typing. Make sure to choose `patreon` since that is how you paid for the whitelabel bot. **Giveaway Key is not used here.** - -- *If `Patreon` is not a selectable option, then your premium perks are already applied to the server.* - - - -**And you're done!** Your bot should be ready for use. - -There are a few more **optional** steps below, if you wish to take them. - - -## Optional: Set Custom Status -You can optionally change your custom bot's status. Simply enter the new status on the dashboard and press `Submit`. - -`Playing`, `Listening`, `Watching`, `Competing` and `Custom` are all currently available. - - - - -## Optional: Set Privacy Policy & ToS Links -On the `General Information` tab of the Discord developer portal, you may have noticed `Terms Of Service URL` and `Privacy Policy URL` fields. - -You should enter our policies here to inform users of how their data may be used. - -**Terms Of Service:** https://tickets.bot/terms-of-service -**Privacy Policy:** https://tickets.bot/privacy - - diff --git a/src/setup/auto.md b/src/setup/auto.md deleted file mode 100644 index e353d41..0000000 --- a/src/setup/auto.md +++ /dev/null @@ -1,14 +0,0 @@ -# Bot Configuration: Automatic Setup -*** - -Tickets provides an option to automatically create a basic configuration for you. This isn't recommended since the settings are unlikely to be to your preference, and a ticket panel is **not** automatically created. For information on creating ticket panels, see our guide [here](./panels.md). - -To run the automatic setup mode, first ensure that you are either the owner of the server, or the owner has designated you as an administrator of the bot using `/addadmin @YourUsername`. Next, simply execute `/setup auto` in a channel the bot can see. - -It will update you as the process progresses: - - - -Simply assign your support staff the new `Tickets Support` role and your administrators the `Tickets Admin` role and your staff will be able to open and support users in tickets created via `/open` or the context menu (right click > apps > start ticket.) - -You'll probably want to [create a ticket panel](./panels.md) so it's easier for your server members to open a ticket, or tweak the settings on the [web dashboard](./dashboard.md). \ No newline at end of file diff --git a/src/setup/configuration.md b/src/setup/configuration.md deleted file mode 100644 index baa0f2d..0000000 --- a/src/setup/configuration.md +++ /dev/null @@ -1,27 +0,0 @@ -# Bot Configuration -*** - -Let's start getting the bot ready for use in your server! - -Tickets was a very early adopter of slash commands, meaning that you can simply hit `/` in your Discord client to have commands auto-completed with the correct arguments: - - - -If you're not the owner of the server, now would be a good time to get the owner to designate you as an admin of Tickets. You can do this by asking the owner to run the command `/addadmin @YourUsername` in a channel the bot can see. If successful, Tickets will show you a β . - -We've created a few different ways in which you can configure the bot: -- Via the [web dashboard](https://dashboard.tickets.bot) **[Recommended]** -- Via `/setup` - - Auto - - Individual Settings - -> **Note:** We recommend using the web dashboard to configure the bot, as it's easier and more settings are available - including ticket panels. - -If you'd prefer to stick to configuring the bot via commands in Discord, there are a few different methods in which you can do so: -- `/setup auto` will automatically create roles, channels, and everything else you need (excluding reaction panels) without any interaction required from you. This is okay for simple usecases, but you'll likely want to configure the options yourself. -- **Individual Settings**: Run commands such as `/setup limit` and `/setup use-threads` to change individual settings one by one. - -We have guides on each of the available methods: -- [Web Dashboard](./dashboard.md) **[Recommended]** -- [Auto](./auto.md) -- [Individual Settings](./individual.md) diff --git a/src/setup/dashboard.md b/src/setup/dashboard.md deleted file mode 100644 index 1838da8..0000000 --- a/src/setup/dashboard.md +++ /dev/null @@ -1,93 +0,0 @@ -# Bot Configuration: Web Dashboard -*** - -First, head over to the dashboard at [dashboard.tickets.bot](https://dashboard.tickets.bot). You'll be asked to login with Discord - simply click `Authorize` and you'll be taken back to the dashboard. - - - -A list of servers which you are a Tickets bot administrator (`/addadmin`) and the bot has been invited to should show up. Simply click on the server you want to configure. If the server does not show up, ensure that you are either the owner of the server or have been added as a Tickets bot administrator by the owner using `/addadmin @YourUsername` and log out of, then back into, the dashboard. - - - -You'll be taken to the settings page as follows: - - - -You'll first want to pay attention to the main **Settings** card. Here you can edit the following settings: - -## Per User Simultaneous Ticket Limit - -This is the amount of tickets that a **single user** can have open **at a single time**. We usually recommend setting this to 1, but the default is 5. - -For example, if you set this value to 1, a user will be able to open and close tickets an infinite amount of times, but only have a single ticket open at once. This value does not affect the total amount of tickets that can be opened at once in a server. - -We do not impose any limits on the amount of tickets that a server can have open at once. However, please note that Discord only permits a total of 500 channels to exist in a server at once, and 50 channels to exist at once in a category. This means that you can move tickets to a new category if one gets filled, however you are limited to 500 channels overall by Discord. - -## Allow Users To Close Tickets - -This option specifies whether users are allowed to close their own tickets. If unchecked, only your support staff & administrators will be able to close them. - -## Ticket Close Confirmation - -This option specifies whether Tickets will send a confirmation message when closing a ticket via the π`close` reaction. If checked, Tickets will send the following message after reacting: - - - -Simply click the blue βοΈ`close` reaction to confirm you want to close the ticket. - -Close confirmation does not apply to tickets closed using the slash command `/close`. - -## Welcome Message - -The welcome message is the message displayed in the Ticket as soon as the user opens it: - - - -> **Note:** the message has a maximum limit of 1024 characters due to Discord limitations. - -- You may make use of placeholders in your welcome message. You can view a list of placeholders [here](../miscellaneous/placeholders.md). - -- You may also use discord message formatting to include links to channels, emojis, roles, or usernames in your welcome message. **First**, you will need to have discord developer mode turned on - in your personal discord account settings > advanced > discord developer mode. **Second**, you can right click any channel name, username, message, etc and choose `Copy ID`. **Third**, use the `structure` section of [discord's messge formatting chart](https://discord.com/developers/docs/reference#message-formatting) to include it in your welcome message. - -The title of the embed will either be based off of the subject provided by the user when using `/open [Subject]`, or the title of the ticket panel if used. We are unable to get a subject from the user when using ticket panels currently, however, this will be possible in a future update of Discord. - -## Transcripts Channel - -When Tickets are closed, a transcript will automatically be recorded, encrypted, and stored in cloud based object storage - with no user interaction required. - -A message, similar to the one following, will also be sent to your transcripts channel to notify you the ticket was closed and provide you with a link to the dashboard to view the archive: - - - -This message will also be sent via direct messages to the user who opened the ticket. It is not possible to disable this functionality since we believe it is important for transparency purposes that users are also able to access the transcripts. - -If you have privacy concerns, please join our [support server](https://discord.gg/ticketsbot) to enquire. Unfortunately we are unable to answer any questions regarding your user data off-platform in order to verify your identity. - -## Channel Category - -Designates the channel category that tickets will be created under. If you are unsure what a channel category is, Discord has a guide explaining them available [here](https://support.discord.com/hc/en-us/articles/115001580171-Channel-Categories-101). - -Your tickets will be grouped together under the category as follows: - - - -## Overflow Category - -Discord has an imposed limitation that each Channel Category can only hold 50 channels. Once you hit this limit, Tickets bot will fail to be able to open more ticket channels for you and your server members. To help rectify this, you can set an Overflow Category. This is a category that the ticket channels will open in once your selected Channel Category has hit the Discord imposed limit. - -## Naming Scheme - -Defines how the ticket channels should be named. Currently, the 2 options are by ticket ID (`#ticket-1`) or by username (`#ticket-name`). You can define more [custom naming schemes](./panels.md#naming-scheme) in the settings of individual reaction panels, instead of this overall setting. - -## Submission - -Once you are satisfied with your settings, press the `Submit` button to save them. An example follows: - - - -We now have the basic configuration completed! - -You may wish to configure the following options next: -- [Ticket Panels](./panels.md) -- [Claim Settings](../dashboard/settings/claiming.md) -- [Auto Close](../dashboard/settings/settings.md/#auto-close) diff --git a/src/setup/individual.md b/src/setup/individual.md deleted file mode 100644 index fb87824..0000000 --- a/src/setup/individual.md +++ /dev/null @@ -1,42 +0,0 @@ -# Bot Configuration: Indiviual Commands -*** - -You can also tweak individual settings by using a single command. Note, not all settings are available via command, some are only accessible on the [dashboard](./dashboard.md), such as [ticket panels](./panels.md). - -To run the setup, first ensure that you are either the owner of the server, or the owner has designated you as an administrator of the bot by using `/addadmin @YourUsername`. - -For definitions and explanations of settings, please refer to the [dashboard guide](./dashboard.md#ticket-limit). - -## Setup Commands - -| Command | Description | -| ---------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | -| /setup auto | Bot will make a very basic configuration (no ticket panels - you'll still want to customize on dashboard) | -| /setup limit | Change the quantity of tickets a single user can have open at the same time | -| /setup transcripts | Change the transcripts channel | -| /setup use-threads | Change whether thread mode is enabled | - -### Auto -See our guide on auto setup [here](./auto.md). - -### Ticket Limit -An explanation of ticket limits is available [here](./dashboard.md#ticket-limit). The command `/setup limit` is used to configure the ticket limit. - -> **For example:** to change the per user simultaneous ticket limit to `1` **-** Run `/setup limit 1` - -### Transcripts -An explanation of transcript channels is available [here](./dashboard.md#transcripts-channel). The command `/setup transcripts` is used to configure the transcripts channel. - -> **For example:** to change the transcripts channel to `#logs` **-** Run `/setup transcripts #logs` - -- _Please note, the channel must already exist._ - -### Use Threads -It is recommended to read an explanation of thread mode (and how it compares to channel mode) [here](../features/thread-mode.md) before using this command. The command `/setup use-threads` is used to enable (`true`), or disable (`false`), whether tickets open as private threads instead of channels. It will also be necessary to select the ticket notification channel. - -> **For example:** to enable thread mode **-** Run `/setup use-threads`, choose `true`, click `ticket_notification_channel`, then select the channel desired from list - -- _Please note, the selected channel must already exist._ - -## Additional Settings -Additional settings are available on the [dashboard](./dashboard.md), such as [ticket panels](./panels.md). It is advised that you read these guides next. diff --git a/src/setup/introduction.md b/src/setup/introduction.md deleted file mode 100644 index 39d1393..0000000 --- a/src/setup/introduction.md +++ /dev/null @@ -1,27 +0,0 @@ -# Setup -*** - -Thanks for choosing Tickets as your support solution! In this guide we'll teach you how to get up and running in no time at all. - -> If you need any assistance in the process, feel free to join our [Discord server](https://discord.com/invite/ticketsbot) and open a ticket to talk to our support staff. - -### For those with previous experience configuring Discord bots -*** -Quickly get the absolute basic functions of a ticket system for your server in 5 steps: - -**1.** [Invite the bot](https://invite.tickets.bot) -**2.** Make yourself admin of the bot `/addadmin @YourUsername` -**3.** Go to the [web dashboard](https://dashboard.tickets.bot) -**4.** Make a [ticket panel](../setup/panels.md) -**5.** Go back to discord and add your staff as support so they can see and answer tickets `/addsupport @TheirRole` - -> It is **HIGHLY RECOMMENDED** to continue reading through SETUP and the rest of the documentation, as these steps only provide the most basic working ticket system. There are many ways to customize the system, messages, notifications, and support staff. - -### For beginners with Discord bots -*** - -You'll need to start by inviting Tickets to your server. -- *Learn how to do this [here](../setup/invite.md).* - -**If you've already invited the bot to your server**, feel free to jump ahead and start configuring it. -- *View our guide on this [here](../setup/configuration.md).* diff --git a/src/setup/panels.md b/src/setup/panels.md deleted file mode 120000 index 628512f..0000000 --- a/src/setup/panels.md +++ /dev/null @@ -1 +0,0 @@ -../dashboard/reaction-panels.md \ No newline at end of file diff --git a/src/setup/staff.md b/src/setup/staff.md deleted file mode 100644 index 1479e87..0000000 --- a/src/setup/staff.md +++ /dev/null @@ -1,26 +0,0 @@ -# Support Staff -*** - -Now that the ticket system is in place, Tickets bot needs to know which of your staff should have access to the tickets (and the online dashboard settings - if desired.) - -> **There are two scenarios for how to setup support staff:** -> - Staff members handle **SPECIFIC** tickets -> - Staff members handle **ALL** tickets - - -## Staff members handle SPECIFIC tickets -*** -> Setting the support staff in this scenario can only be accomplished via the [web dashboard](https://dashboard.tickets.bot). A guide on this can be found [here](../dashboard/staff-teams.md). - - -## Staff members handle ALL tickets -> Setting the support staff in this scenario, is recommended via slash commands. - -**Command:** `/addadmin @username` or `/addadmin @role` - -Not only does this add the specified user to the Default Team in Staff Teams, but it also gives that user full administrative privileges of the Tickets bot for your server. This is just having admin of the Tickets bot, **not your server**. -- Having admin privileges of the bot means the user will be able to use the [web dashboard](https://dashboard.tickets.bot) fully, and control all the configuration, settings, customization of the bot, as well as see ALL of the tickets/transcripts contained there. ***Only give this privilege to those you trust.*** - -**Command:** `/addsupport @username` or `/addsupport @role` - -This adds the specified user to the Default Team in Staff Teams. The only thing they will be able to see on the web dashboard are the tickets where the Default Team has been assigned as a support team. diff --git a/src/vid/Forms.mp4 b/src/vid/Forms.mp4 deleted file mode 100644 index ea2ad0d..0000000 Binary files a/src/vid/Forms.mp4 and /dev/null differ diff --git a/src/vid/ReactionPanels.mp4 b/src/vid/ReactionPanels.mp4 deleted file mode 100644 index 4e63e09..0000000 Binary files a/src/vid/ReactionPanels.mp4 and /dev/null differ diff --git a/src/vid/StaffTeams.mp4 b/src/vid/StaffTeams.mp4 deleted file mode 100644 index 0f62b61..0000000 Binary files a/src/vid/StaffTeams.mp4 and /dev/null differ diff --git a/theme/favicon.svg b/theme/favicon.svg deleted file mode 100644 index 4d9c4c3..0000000 Binary files a/theme/favicon.svg and /dev/null differ