Permissions

The organization system does not assume every team member should control every part of the team.

That is why access is split into two layers:

• organization-wide permissions
• car-scoped permissions

This is one of the main reasons two users can belong to the same organization and still see different controls.

The Two Permission Layers

Organization-Wide Permissions

These permissions grant access across the organization.

If a user has one of these, they usually do not need the narrower car-scoped version for the same area.

Examples include:

• admin controls
• finances
• contracts
• sponsors
• upgrades
• cars
• driver assignments

These are the broader management permissions.

Car-Scoped Permissions

These permissions grant access only for a specific car.

Examples include:

• car finances
• car sponsors
• car operations

This is useful when someone should manage one car without gaining full access to the entire organization.

The Most Important Rule

Organization-wide permission usually overrides the need for the narrower car-level version.

In plain terms:

• if a user has broad sponsor access, they do not need separate car sponsor grants for that same organization
• if a user has broad finance access, they do not need separate car finance grants for the accounts they are already allowed to manage through the organization level

This is why some team members see more than others even when nobody manually assigned car-level grants to them.

Organization-Wide Permissions in the Live System

The current organization-wide permissions are:

Admin Controls

What it usually affects:

• organization administration
• member access management
• higher-level management actions

Finances

What it usually affects:

• organization finance workspace
• organization account visibility
• broader finance access across the team

Contracts

What it usually affects:

• contract builder access
• contract offer management
• amendment and extension workflows

Sponsors

What it usually affects:

• organization sponsorship management
• relationship and emergency sponsorship workflows
• sponsor access across cars in scope

Upgrades

What it usually affects:

• upgrade-related team controls as those flows are surfaced

Cars

What it usually affects:

• car management actions
• entry-level organization operations

Driver Assignments

What it usually affects:

• race assignment workflows
• operational driver placement by car and event

Car-Scoped Permissions in the Live System

The current car-scoped permissions are:

Car Finances

What it usually affects:

• visibility into a specific car account
• car-level financial review without broader organization finance control

Car Sponsors

What it usually affects:

• sponsorship management for a specific car
• sponsor schedule and relationship work for that entry only

Car Operations

What it usually affects:

• entry-level operational control for that car
• assignment-style workflows tied to that entry

Why a Page May Be Missing

If a user cannot see a page or control, do not assume the feature is broken.

The most common causes are:

1. the user is not an active member of the organization
2. the user does not have the required organization-wide permission
3. the user does not have the required car-scoped permission for that entry
4. the owner-only role restriction is in effect

That is the correct order to check.

Common Permission Patterns

�I can see one car account but not the organization account.�

That usually means the user has car-scoped finance access but not broad organization finance access.

�I can manage sponsors on one car but not another.�

That usually means the user has car sponsor scope on one entry, not organization-wide sponsor permission.

�I can see the organization, but I cannot send contracts.�

That usually means the user is a valid member but does not have contract management permission.

�I can view the team, but not edit members or owner-level settings.�

That usually means the user is not the owner and does not have the necessary admin-level permission.

Owner Role

The organization owner is treated differently from regular members.

In practice, the owner has the broadest level of access and is not expected to operate like a regular scoped member.

That is why owner controls and ownership-transfer workflows are not handled the same way as normal permission editing.

Practical Troubleshooting Order

If access looks wrong, check in this order:

1. is the user an active member of the organization?
2. is the user supposed to have broad organization access or only car-level access?
3. is the missing function tied to contracts, sponsors, finances, or operations?
4. is the specific car in scope for the member?

That will usually explain the missing page or missing button quickly.

Final Reminder

Permissions are one of the main reasons the dashboard looks different from user to user.

If a feature seems to be missing, the first question should not be �is the system broken?�

The first question should be �does this user actually have the right scope to see it?�