Workspace settings

The hosted Settings page controls which ACSM events receive RaceControl and which Steam accounts may receive each interface. It is available to an organization with an active license.

Choose ACSM events

Install the connector first so it can publish the events it finds. In Target ACSM events, search or filter the catalog, choose the events to enable and save. You can select all available events or maintain a selected list. The connector checks the saved policy about every five minutes and applies or removes only the RaceControl-managed CSP block for each event.

A listed event is not necessarily live: ACSM must load that event, and the Assetto Corsa server must be reachable. Plan the initial event load or server restart for a safe moment; saving Settings does not restart the game server.

If no events appear, check the ACSM root supplied to the connector and its systemd timer. See installation and troubleshooting.

Decide who receives each interface

The Race Control permissions section has separate audiences for the driver HUD, broadcast interface, Track Limits organizer and debug tools. Each can allow everyone, allow only selected SteamIDs or allow everyone except selected SteamIDs. Use the lists or enter a 17-digit SteamID manually. The connector publishes known drivers from ACSM, but you can still enter an ID that is not listed.

Save the page after changing any audience. A connected driver may need a fresh authentication or live update before a new permission takes effect. These audiences control RaceControl features; they do not replace ACSM server admission or event rules.

A practical first configuration

1. Link one server in /account.
2. Enable one known ACSM event in /settings.
3. Leave the driver HUD audience open to all drivers if everyone in that event should see flags and messages.
4. Keep broadcast, organizer and debug audiences limited to the SteamIDs that actually need those tools.
5. Wait for the connector sync, or run its --sync command on the Linux host, then load the configured event at a safe time.
6. Confirm the HUD with a compatible Assetto Corsa/CSP client before relying on it in a race.

For live actions, see Race direction console.

Customize organization logos

Available in HUD 1.5.6 and later. Reconnect to your game server to load the current HUD before testing your logos.

In Settings → Customize HUD logos, upload your Organization logo once to reuse it across the HUD. You can choose a separate logo for the welcome panel, race-direction notices, radio, flag display and Track Limits. Broadcast also has header and replay logo slots. The RaceControl signature is fixed.

1. Choose Upload a PNG and select an image (at most 2 MB). Interlaced or larger images are converted automatically to non-interlaced RGBA at 2048 px max. Transparent backgrounds work best.
2. Check the preview. Images keep their original proportions; they are not stretched or cropped.
3. Leave each surface on its organization default, upload a different image, or select Hide logo. Use organization logo removes an individual override. Remove default logo removes only the shared logo; individual overrides remain.
4. Click Save HUD logos. This saves branding separately from audiences and events. Connected drivers receive saved logos automatically, even during a session (the loader refreshes the remote options in place without replacing the app). No server reinstall or license rotation is needed.

Uploaded images are visible to drivers. Only your organization’s signed-in workspace can change its selections. Existing local broadcast artwork remains in use until an organization logo or a broadcast override is chosen. Car manufacturer badges in broadcast rows are vehicle identification, separate from organization branding.