-
ONE RACEHUB uses multiple permission controls to manage access to features, data, and actions.
💡Tips:
-
Each user’s role determines which features they can access.
-
Their team assignment controls which team’s records they can edit. You can further restrict access to selected events or cars.
For more information on sidebar feature visibility, see Roles and Permissions and Sidebar Visibility by Role.
How Editing Permissions Work
To edit a record, a user must meet the applicable permission requirements. These may include:
- Role: The user's assigned role must allow the editing action.
- Team assignment: The user must belong to the team associated with the record, unless they have an applicable cross-team override.
- Record status: Locked records are read-only for all users.
- Contestant restrictions: If configured, the contestant must be included in the user's Editable Contestant IDs list.
The exact requirements depend on the type of record.
Run Sheet and Setup Sheet Editing
Editing permissions for RunSheets and Setup Sheets vary by role:
Important notes:
- Run sheet editing is designed to let operational team members update session information while protecting data from other teams. MECHANICS can edit eligible run sheets but can only view setup sheets.
-
Locked run sheets cannot be edited by any user.
Parts Management Access
Parts visibility depends on the user’s role and team assignment.
|
Access level |
Roles |
|
View parts across all teams |
ADMIN, CE, MGMT, WM |
|
View team parts only |
All other roles |
Users with team-restricted access only see parts assigned to their own team.
This helps reduce clutter and prevents users from accidentally working with another team’s parts data.
User Management Permissions
User management actions are restricted to ADMIN and MGMT users.
|
Action |
Allowed roles |
|
Create, edit, and delete users |
ADMIN, MGMT |
|
Assign users to teams |
ADMIN only |
|
Assign default run sheet style |
ADMIN only |
|
Configure individual user restrictions |
ADMIN, MGMT |
⚠ Only ADMIN users can assign teams. This prevents users from changing team access in a way that could expose another team’s data.
Individual user restrictions include:
- Visible Events: Determines which events a user can access.
- Editable Contestants: Determines which contestants a user can modify.
- Hide KPIs: Determines whether KPI information is hidden from the user.
For further information, see Configure Individual User Access and Configure Individual Event Access.
How ONE RACEHUB Decides What a User Can Access
-
User access is evaluated in four levels: Assigned Role, Team, Event, and Individual User Access.
KPI Dashboard Access
KPI Dashboard access requires both role permission and an individual user access configuration.
|
Requirement |
Details |
|
Allowed roles |
ADMIN, MGMT, CE, C-ENG, MECH |
|
Required user profile setting |
|
-
If the user has an allowed role but
hideKPIsis enabled, the KPI Dashboard is hidden.
ⓘ Use hideKPIs setting to restrict access to sensitive performance data for selected users.
To learn how to hide KPIs for individual users, see Configure Individual User Access.
Time Tracker Access
Time Tracker access is controlled in Configuration → Admin → Users / Drivers.
|
Feature |
Role condition |
Required profile flag |
|
Time Tracker |
All roles except DRV |
|
|
Export / Admin functions |
All roles except DRV |
|
A user must meet both the role condition and the required profile flag condition.
Use these flags to enable time tracking for selected users and restrict administrative time tracking functions to approved users.
Team-Based Data Access
ⓘ ONE RACEHUB supports team-based data isolation. When a user is assigned to a team, they can only access data associated with that team, unless their role allows access across teams.
To learn how to assign users to a team, see Manage Users and Drivers.