ResourcesBenefitsTry itReviewsContact
Create account

Vanta / Support / Existing customer

Support for resources
you already own.

Installation, updates, unexpected behaviour and licence questions — with a clear checklist so support can get to the useful part quickly.

01
Start here

Before opening a request

A good support request contains the information needed to reproduce the problem. That avoids several rounds of basic questions and makes it easier to separate configuration issues from real bugs.

  • Your order, purchase or licence reference.
  • The exact Vanta resource name and version.
  • Your FiveM artifact/build plus ESX, QBCore or other framework version where relevant.
  • A short, repeatable set of steps that causes the issue.
  • Relevant console output, logs or screenshots with passwords, tokens and private keys removed.
02
Installation & updates

Get the resource running cleanly

For installation or update issues, work from a known-good baseline. Confirm dependencies first, keep custom edits separate, and compare your configuration against the current documentation before changing multiple things at once.

  • Confirm every documented dependency is installed and started in the required order.
  • Check that your server artifact and framework versions meet the product requirements.
  • Back up your current resource and configuration before updating.
  • Test the stock configuration before reapplying local customisations.
  • Restart the affected resource or server after database or dependency changes when required.
03
Bug reports

Help us reproduce the exact behaviour

A useful bug report explains what should have happened, what actually happened and the smallest sequence of actions that reproduces it. Include evidence from both the client and server where the issue spans both sides.

  • Expected result and actual result.
  • Exact steps to reproduce from a clean restart when possible.
  • Client F8 errors and server console errors that appear at the same time.
  • Whether the issue happens for every player or only certain roles, jobs or identifiers.
  • Any third-party resource that modifies the same system or event flow.
04
Licences & account

Purchases, access and licence questions

Keep purchase access tied to the account that completed the order. If a server, owner or organisation changes, contact support before moving files or licence access so the correct route can be confirmed.

  • Use the purchasing account when asking about downloads or order history.
  • Include the order reference when asking about a missing purchase.
  • Do not publish or share licence keys, tokens or private download links.
  • Check the product licence before moving a resource between servers or organisations.
  • For a lost account or changed email address, provide enough purchase information for ownership to be checked safely.

Quick answers

Common questions.

Can I send my whole server folder?

No. Send only the minimum relevant logs, screenshots, configuration excerpts and reproduction steps. Never send credentials, database passwords, Discord tokens or other secrets.

Should I edit the resource while troubleshooting?

Start from the stock resource and a minimal configuration where possible. That makes it much easier to tell whether the problem is in the original resource, configuration or another integration.

What if the issue started after an update?

Include the previous working version, the new version and any migration steps you followed. Mention whether reverting restores the previous behaviour.

Can support help with unrelated third-party scripts?

Support can explain documented integration points and help identify conflicts involving a Vanta resource, but another developer’s code may need to be handled by that product’s maintainer.

READY TO OPEN A REQUEST?

Send the useful details once.

Include the resource, version, framework/build, reproduction steps and relevant evidence. Remove all secrets before sending anything.

Email support ↗Back to contact