Manual › Chapter 06

The team

Creating a team, roles and permissions, badges, roster, standing crews, shared files, public page and alliances.

What a team is#

A team is the container for everything else: events, crews, stints, shared files, team telemetry. You can belong to several teams at once, and each has its own roster and calendar.

The Teams tab lists your teams; opening one gives you the Members, Requests (for admins), Management and Files tabs.

Joining, creating, leaving#

Creating a team#

Create team, give it a name, done: you become admin and owner. The invite code to hand out is in Teams → Management.

Joining a team#

With the invite code (8 characters) entry is immediate. If the team has a public page and accepts applications, you can also apply and wait for an admin to answer.

Leaving#

Leave team, with confirmation. An owner cannot leave if they are the last one: they must first appoint another or hand the team over.

Roles and permissions#

There are three levels, and they should not be confused.

Only an owner can appoint or remove admins. A team must always have at least one owner.

➡ Hand over the team transfers ownership to someone else; whoever hands it over stays an admin.

Badges, and what they open#

Every driver can be given a badge — Platinum, Gold, Silver, Bronze — assigned by admins based on attendance and activity. It is not just recognition: it governs what that driver sees of the shared material.

For each level you choose access to four things:

Admins and owners are always Platinum. And every driver always sees their own data, whatever badge they hold.

A badge also carries a reason visible to the driver: worth writing, because a level with no explanation reads like a verdict.

The roster#

Drivers with an account#

They have an EndurancePRO account: companion, telemetry, notifications and sign-ups all work for them.

Manually added drivers#

Drivers without an account, added by an admin. They appear in the roster and on the cards — liveries, data — but with no automation: no companion, no telemetry, no notifications, no sign-ups. Their data is maintained by the admin.

They exist so the roster has no holes while you wait for someone to register. When they do register, 🔗 Merge into an existing driver transfers number, colours and data onto the real account and deletes the duplicate.

Importing from a file#

📋 Import roster from file loads the team's spreadsheet, xlsx or csv. Columns are recognised from their headers: name, number, colour, nationality, cust id. Drivers already present are updated, not duplicated.

Before importing you see what will happen: how many rows were found, how many will be created, how many updated and which numbers are duplicated — those are not assigned.

Management#

Identity#

Name, description and the team logo (PNG, JPG or SVG up to 2 MB), which appears on the team page and, if you want, in the broadcast graphics.

Public page and applications#

Public team page switches on a shop window visible without an account: introduction, statistics, palmares. Accept applications adds the apply button.

With the public page off, the team can only be found with the invite code.

Requirements to sign up for events#

Drivers who have not filled in certain profile fields cannot sign up. The fields you can require are: race number, livery colours, nationality, iRacing customer ID, preferred cars, training preferences.

The panel tells you how many drivers are not compliant, so you know whether you are about to lock out half the squad.

Livery colours required from drivers#

One, two or three colours (primary, secondary, accent): how many each driver can declare on their profile.

iRacing teams#

iRacing does not know about our crews: it knows about its own teams, and whoever fields several cars registers one per car. You list them here — NOVA team red, NOVA team green — and then assign them to crews in the race plan.

Deleting the team#

Delete team, with an explicit confirmation: it disappears with all its data.

Standing crews#

The squad's stable line-ups: Red, Green, whatever you like. Each has a class, a car, a crew chief and three groups of people: regulars, reserves, pit wall.

You bring one into a race with a click, and from then on the race owns it: a last-minute change does not rewrite the line-up back home.

Inside a line-up you can also mark a driver as no night or no qualifying: that applies there only, their profile is untouched.

For a single race you can add guests from outside the squad and call up reserves.

Team files#

Setups (.sto), liveries (.tga) and spec maps (.mip). Whoever uploads chooses the recipient: the whole team or a single driver.

The recipients' companions install them into iRacing's folders by themselves, and the livery is renamed with the customer ID of whoever receives it.

To send a livery to one driver there is a shortcut: open their card under Members and use Send livery. The file name does not matter, the system handles it.

Alliances#

Two allied teams share their rosters: you can call up the other team's drivers for an event, with their race paces and their licences.

You propose the alliance, the other team accepts, and it becomes active. Until they accept it stays pending.

The driver and team board#

Where drivers looking for a seat and teams looking for drivers meet.

• Looking for a team — a driver's advert.
• Looking for drivers — a squad's advert; you must be a team admin to post one.

The numbers shown — iRating, licences, paces — come from verified profiles, not from what the advert claims.

Adverts expire on their own after 30 days: re-saving one puts it back on top.

Palmares#

Races, wins and podiums appear on the team's public page. They fill themselves in: every time a debrief is saved to the palmares, the result lands there. See After the race.

Championships#

Championships do not belong to a squad: you enter on your own, even without a team. Anyone looking for a seat can say so, and the panel shows where your teammates are racing — not team races, but you can follow them and practise together on the same track.

Ready for the next round?#

The calendar says where you race, the paces say who has been there. Crossing them is the job nobody does in time, and that you find out about on race night when a driver runs three seconds off the others.

The panel lines up whoever has no reference on that car+track combination, and lets you create the practice session directly.