Understand Team-Based Permissions

ONE RACEHUB uses multiple permission controls to manage access to features, data, and actions. A user's effective permissions may depend on their assigned role, team, contestant restrictions, and profile settings. For sidebar feature visibility by role, see Roles and Permissions overview.

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

Run sheets and setup sheets have different editing permissions.

Permission	Run Sheets	Setup Sheets
Allowed roles	ADMIN, CE, C-ENG, MECH, TE, WM, SR	ADMIN, CE, C-ENG, SR
Same-team requirement	Yes (Team ID match), except ADMIN	Yes (Team ID match), except ADMIN
Editable Contestant IDs	Applies if configured	Applies if configured
Locked records	Read-only for everyone	Read-only for everyone
ADMIN cross-team editing	Yes	Yes

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 advanced 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.

Advanced 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.

KPI Dashboard Access

KPI Dashboard access requires both role permission and a user profile setting.

Requirement	Details
Allowed roles	ADMIN, MGMT, CE, C-ENG, MECH
Required profile setting	`hideKPIs` must be set to `false`

If the user has an allowed role but hideKPIs is enabled, the KPI Dashboard is hidden.

ⓘ Use hideKPIs setting to restrict access to sensitive performance data for selected users.

Time Tracker Access

Time Tracker access is controlled by user profile flags.

Feature	Role condition	Required profile flag
Time Tracker	All roles except DRV	`isTimeTracker`enabled
Export / Admin functions	All roles except DRV	`isTimeTrackerAdmin`enabled

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.

⚠ If a user’s team assignment changes, the user must log out and log back in for the change to take effect.