Configure Advanced User Access
Configure additional access restrictions and security options for individual users after creating their account.
-
After creating a user, you can edit the account to define what data the user can see or change.
-
Use advanced access settings for freelancers, contractors, multi-team environments, or anyone who should only work with selected events or cars.
ⓘ Advanced user settings are configured from Configuration → Admin → Users / Drivers. The available options depend on your role and permissions.
Restrict Access to Events
Use Visible Event IDs to control which events a user can access.
For example, you can use Visible Events to:
- Give a freelancer access to a specific event only
- Restrict a user to the current season
- Prevent access to events from previous seasons
⚠️ Visible Event IDs work as a whitelist. If you create new events later, you must manually add them to the user’s visible events list. Only existing events can be selected.
Event and Contestant Whitelists
Visible Contestant IDs
Use Visible Contestant IDs to control which contestants, cars, or entries the user can see.
This helps keep the user’s workspace focused and prevents access to irrelevant car data.
Use this when you want to:
- Show only the cars assigned to a user
- Hide other garage or team data
- Restrict a freelancer to one car
Example: Give a mechanic visibility for Car #23 only. When a contestant is visible to a user, events where that contestant participates are also made available to that user.
Editable Contestant IDs
Use Editable Contestant IDs to control which contestants, cars, or entries the user can modify.
A user may be able to see more data than they can edit. Use this setting to prevent accidental changes to the wrong car.
Use this when you want to:
- Allow a user to view several cars but edit only one
- Keep freelancers restricted to their assigned vehicle
- Prevent data entry in the wrong contestant record
Example: A freelance engineer can view Car #45 and edit only Car #45.
|
Access goal |
Recommended setting |
|
User should only see one event |
Use Visible Event IDs. |
|
User should see all events for one car |
Use Visible Contestant IDs. |
|
User should only edit one car |
Use Editable Contestant IDs. |
|
User should work on one car at one event only |
Use Visible Event IDs, Visible Contestant IDs, and Editable Contestant IDs together. |
Additional Security Options
Disable User
- Prevents login access without deleting the account
- Useful for temporary restrictions or when someone leaves the team
- Preserves historical data associations
- User appears as "Inactive" in the Users / Drivers list
Hide KPIs
Use Hide KPIs to prevent a user from accessing the KPI Dashboard, even if their role would normally allow KPI access.
Use this for:
- Protects sensitive car performance data
- External personnel
- Freelancers or contractors
- Users who should not see complete performance data
ⓘ KPI access also depends on the user’s role. For role-based access details, see Roles and Permissions.
Example configurations
Mechanic assigned to one car
Configuration:
|
Field |
Example |
|
Name |
John Smith |
|
Role |
Mechanic |
|
Username |
john.smith |
|
|
|
|
RunSheet Style |
Mechanic Layout |
|
Visible Events |
Current season events |
|
Editable Contestant IDs |
Car #23 |
|
Hide KPIs |
Disabled |
Result: John can work with Car #23 in the selected events, but does not get broader editing access.
Multi-team environment
Use team assignment when multiple teams work in the same ONE RACEHUB instance.
Example setup:
|
User |
Role |
Team |
Visible Contestants |
|
Sarah Johnson |
Car Engineer |
Ferrari GT3 |
Ferrari GT3 cars |
|
Mike Chen |
Car Engineer |
Mercedes GT3 |
Mercedes GT3 cars |
Result: Both users work in the same ONE RACEHUB instance, but only access the data assigned to their team.
⚠️ After changing a user’s team, ask the user to log out and log in again.
Best practices
- Use Visible Event IDs for short-term event access.
- Use Visible Contestant IDs when access should follow a car across events.
- Use Editable Contestant IDs to prevent changes to the wrong car.
- Use Hide KPIs for external users who should not see sensitive performance data.
- Deactivate users instead of deleting them when their historical records should remain intact.
- Regularly audit user roles and active status, especially at the start and end of each season.