Configure Individual Event Access
Restrict a user's access to specific events, seasons, or race weekends in ONE RACEHUB.
Use Visible Event IDs to control which events a user can access. For example, you can:
- Give a freelancer access to one race weekend
- Restrict a user to events in the current season
- Prevent access to events from previous seasons
- Limit temporary staff to their assigned events
ⓘ Event access settings are configured in Admin panel. The available options depend on your role and permissions.
Configure event access
- Go to Configuration → Admin → Users / Drivers
- Select the edit icon for the user you want to configure
- Open the Visible Event IDs dropdown
- Select the + icon next to an event or series to expand it
- Select the checkbox next to each event the user should be able to see
- Select Save
⚠︎ Only existing events appear in the list.
How the event whitelist works
Visible Event IDs works as a whitelist. It determines which events a user can access.
- One or more events selected: The user can access only the selected events.
- No events selected: No event restriction is applied through this setting.
⚠️ If you create new events later, users with a restricted event list do not receive access to them automatically. To grant access to a new event, add it to the user's Visible Event IDs list.
Restrict access by season or event
Select the events that match the user's responsibilities.
| Access goal | Configuration |
|---|---|
| User should access one race weekend only | Select only that event |
| User should access the current season only | Select the events from the current season |
| Contractor should support selected events only | Select only the assigned events |
Combine event and contestant restrictions
-
Use event restrictions together with contestant restrictions when a user should work on specific cars only at specific events.
Example: A freelancer should work on Car #23 at one event only.
| Setting | Configuration |
|---|---|
| Visible Event IDs | The selected event only |
| Visible Contestant IDs | Car #23 |
| Editable Contestant IDs | Car #23, if the user should edit that car |
⚠︎ Visible Event IDs and Visible Contestant IDs are configured separately. Check that the event and contestant selections match the user's assigned work.
For details about contestant access and editing permissions, see Configure Individual User Access.
Example configuration: Restrict a freelancer to one event
Suppose Alex Morgan is an engineer assigned to Car #45 for Event A.
| Setting | Configuration |
|---|---|
| Name | Alex Morgan |
| Role | Engineer |
| Visible Event IDs | Event A |
| Visible Contestant IDs | Car #45 |
| Editable Contestant IDs | Car #45 |
Result: Alex can work only with Car #45 in Event A.
Best practices
- Use Visible Event IDs for short-term or event-specific access.
- Review restricted event lists whenever new events are created.
- Update event access at the start and end of each season.
- Remove event access when a freelancer, contractor, or temporary user no longer needs it.