Vitality Admin Ecosystem

Overview

Vitality Admin Ecosystem combines an in-game staff interface and a web Control Center. The published product covers moderation, player management, community reports, cases, warnings, bans, watchlists, logs, economy review, and staff auditing.

It is sold for QBOX and delivered through Cfx Asset Escrow. The Control Center is a separate web component, not a generic FiveM NUI-only dashboard.

Before installation

1. Download the purchased files and inspect the exact resource directories, manifests, and included deployment instructions.
2. Back up your server configuration and relevant admin data before replacing any current admin resource.
3. Confirm your QBOX environment and required service access.
4. Plan a private HTTPS URL for the Control Center; never expose admin credentials, tokens, or database passwords in public website files.

The current website catalogue does not include a verified admin package manifest or specific service commands. For this product, follow the versioned deployment README supplied with the purchase; do not assume the folder names or environment variables of a different build.

Staff and permissions

Restrict elevated access to explicitly authorized staff. Configure roles/groups using the release's own server-side permission settings, then check that each role sees only its intended actions.

Test report review, warning/ban workflows, audit logs, and player access from separate non-admin and staff test accounts before making the Control Center available publicly.

Control Center

The Control Center offers web-based reports, server logs, economy review, player activity, server monitoring, and branding settings. Serve it behind HTTPS and configure authentication using the release's deployment instructions.

Keep sensitive endpoints and any server/database credentials on the backend. Avoid sharing a privileged session across accounts.

Troubleshooting

• In-game staff menu is missing: verify QBOX, the installed resource name, permissions, and server/client console errors.
• Web Control Center cannot connect: verify the service is running, its configured origin/API URL and HTTPS proxy settings.
• Permissions seem incorrect: audit server-side roles and test with a non-admin account.
• Need precise deployment variables: consult the purchased package's matching-version README or Vitality support; the exact service configuration is not verified in this public guide.