For staff
Dashboard
Manage submissions, tickets, releases, branding, storage, and analytics from the web
The Vektra dashboard is the web control surface for Pro and Pro+ servers. It uses Discord login, then shows the servers where you can manage Vektra.
What the dashboard can do
| Area | What it does |
|---|---|
| Overview | Shows recent activity, demo counts, open ticket counts, and daily charts. |
| Submissions | Review demos, update status, approve, reject, DM artists, and open track links. |
| Tickets | Review support tickets, change ticket status, resolve tickets, and DM users. |
| Releases | Submit releases for Vektra QC and track accepted or rejected release status. |
| Analytics | View submission and decision trends with line charts and staff workload data. |
| Branding | Edit display name, submit panel caption, embed color, tutorial panel templates, footer, and logo. |
| Messages | Post custom embeds or plain messages to any channel the bot can access. |
| Settings | Change demo intake, storage, staff channels, templates, ticket channels, and post panels. |
| Pro+ Bot | Configure hosted white-label bot identity for Pro+ servers. |
Login and server access
- Open the dashboard at vektra.games.
- Log in with Discord.
- Pick a server from the server dropdown.
The dashboard checks your Discord permissions. You need to be the server owner, an admin, or have Manage Server permission to see the server in the dashboard.
Reviewing submissions
From the Submissions page, staff can:
- Change a demo's status.
- Open a review form with rating, reviewer, shortlist, priority, decision reason, and staff notes.
- Approve or reject a submission.
- DM the artist from the dashboard.
- Open the submitted demo link.
When a dashboard approval or rejection is saved, Vektra can DM the artist and update the original Discord staff card if the submission has stored message references.
Reviewing tickets
The Tickets page keeps support work separate from the demo queue.
- Move tickets between Open, Waiting, Answered, and Resolved.
- Send a DM reply to the ticket opener.
- Keep the private Discord ticket channel as the staff record.
User replies still route back through Vektra when the user replies directly to the bot's DM message.
Release requests
Release requests are for labels that want Vektra QC before Labelcaster delivery.
From Discord, admins can use:
/make-release
/check-releases
From the dashboard, server admins can use the Releases page to submit a release with separate fields instead of a single AI-parsed paragraph. Dashboard release submissions do not use SambaNova metadata checks because the form asks for the required metadata directly.
Required release fields:
- Label name
- Album title
- Artists
- Label owner legal name
- Email IDs for every artist and the label owner, clearly mapped to each person
- C line
- P line
- Composers and producers legal names
- Drive or downloadable file link
Optional fields can be left blank and treated as Auto:
- UPC code
- Number of tracks
- Version titles or names
- Track titles
- Release date
- Genre
- Explicit content
- ISRCs
The release appears in the configured Vektra QC channel with a private discussion thread. Accepted or rejected status, decision notes, and rejection reasons are shown back in the dashboard and through /check-releases.
Distribution fee
Free servers can submit release requests, but Vektra takes a 10% service fee on distribution handled through Vektra. The label keeps 90%.
Paid tiers keep 100% of distribution earnings.
Accepting or rejecting releases
The Vektra owner review workspace can accept or reject release requests from the dashboard. A dashboard decision:
- Updates the release request database.
- Updates the Discord QC card.
- Removes the Discord review buttons from that card.
- Logs the decision in the release thread.
- Can DM the submitter with the acceptance note or rejection reason.
Discord QC cards also include Accept and Reject buttons for owner-side review.
Demo intake
From Settings -> Demo intake, admins can open or close demo submissions for the whole server. This applies to every tier and blocks /submit plus submit-panel buttons while intake is closed.
You can also use the Discord command:
/intake open:false message:Submissions are closed while we review the current queue.
Branding and panel templates
The Branding page supports two submit panel styles:
- Simple caption panel uses your display name, tagline, and embed color.
- Tutorial panel adds a custom title, intro text, numbered steps, tips, button label, footer, and logo/thumbnail.
Saved branding is used when you post submit panels from Discord with /post_panel or from the dashboard.
Custom embed posting
The Messages page lets Pro and Pro+ admins compose a custom embed or plain message and post it to any channel the bot can access.
Posting panels
The dashboard can post submit panels and ticket panels into channels the bot can see.
Storage and settings
Pro and Pro+ servers can use the dashboard to:
- Move between managed storage regions.
- Connect a custom Neon or Postgres database.
- Switch from one custom database to another.
- Edit approval and rejection DM templates.
- Edit saved rejection reasons.
- Set the demo staff channel and ticket staff channel.
When storage changes, Vektra migrates existing server data before switching.
Pro+ Bot
The Pro+ Bot page only appears for servers with an active Pro+ plan. It lets the server connect a custom Discord bot application to Vektra hosting.
From this page, Pro+ admins can:
- Enable or disable the hosted custom bot.
- Save the bot client ID.
- Paste or rotate the bot token.
- Set the hosted bot's status type and status text.
- Open an invite link for the custom bot.
- View manager status from the VPS.
The dashboard never shows the stored token again after it is saved. Tokens are stored encrypted.
Manager statuses:
| Status | Meaning |
|---|---|
pending_restart | Settings were saved and the VPS manager has not applied them yet. |
starting | The manager started the custom bot worker. |
online | The worker process is running. |
stopped | The bot was disabled or Pro+ expired. |
error | The manager could not start the worker. Check the token and VPS logs. |
Vektra