Help center for new users and staff.

Your account is the entry point to the platform. Connect Discord, finish the basic profile details and let the system place you into the right VTC space.

• Use Discord as the main identity layer.
• Keep avatar, flag and basic details current.
• Make sure the profile matches the role you hold inside the company.

Joining a VTC should feel calm and guided. The hub gives drivers a place to discover the company, request access and wait for approval without turning it into a long Discord exchange.

1. Open Discover and choose the company you want.
2. Send a request with the details the team asks for.
3. Wait for approval and read the company rules.
4. Finish the setup steps once you are accepted.

The owner flow is built to reduce setup noise. Add branding, write the description, decide what is public and make the hub look like your company before inviting the team.

• Choose a name, logo and color palette.
• Write a short description that sounds human.
• Set the public or private behavior of the company.
• Keep the first launch focused on presentation and access.

This is the heart of the platform. Start it before you drive, keep it running in the background and let it handle trip logging, telemetry and Discord presence automatically.

1. Install the tracker client.
2. Start it before entering ETS2 or ATS.
3. Confirm that Discord RPC is active.
4. Drive normally and let the logbook update itself.

A clean role structure makes the hub easier to manage. Drivers understand where they stand, recruiters know what they can approve and managers can work without clutter.

• Use ranks to define growth and responsibility.
• Use permissions to separate driver, recruiter and manager access.
• Keep sensitive tools out of general member reach.

Recruitment works best when the process is clear. Let people apply from inside the hub, ask only the questions that matter and keep the review flow short enough that staff can move quickly.

1. Open the application form.
2. Add the questions you want answered.
3. Review submissions from the staff side.
4. Accept or reject with a clear reason.

The most useful stats are the ones people can understand quickly. Make the leaderboard easy to read, keep driver IDs current and let finances stay visible without a spreadsheet in sight.

• Use the leaderboard for friendly competition.
• Use achievements to mark milestones and special events.
• Use driver cards to make profiles feel alive.
• Use finances to keep payouts and income transparent.

Plans should be easy to explain. Keep the value visible, keep the upgrade path clear and make sure owners understand which tools belong to each level.

1. Community: A clean starting point for new crews.
2. Supporter: Adds more collaboration and event flow.
3. Elite: Brings the strongest branding and admin tools.

This is where the hub becomes a management tool instead of a driver profile. Support tickets, audit logs, training and bridge tools should all live here so staff can work faster and stay accountable.

• Support Tickets keep driver issues out of private DMs.
• Audit Logs record promotions, kicks and important settings changes.
• Driving Test BETA helps with training and rank checks.
• Fluxy Bridge is the coming Discord integration layer.