Find your grid.
Know your next move.
From your first sign-in to a prepared race team. A practical guide to GridUnion, with real website examples and clear steps for every part of your workflow.
Your racing world, in one place#
GridUnion connects finding a race with the people and preparation needed to run it. Discover events, build a team, organise a car entry and keep the plan connected to Discord.
Find your next race
Use Race to browse events and their individual start slots. Check the simulator, circuit layout, eligible cars, duration and entry requirements before choosing a start.
Bring the right people
Create or join a team, find drivers and support crew, then assign a line-up to the actual car entry.
Prepare together
Build the stint plan, share a setup and use the connected Discord race card for participation. Driver profiles, liveries, rigs and circuit discussions connect the community between races.
Sign in & connect your identity#
Start with your own driver identity. Your linked Discord account lets GridUnion recognise the same person on the website and in race-channel interactions.
Sign in
Choose Sign in on GridUnion and follow the sign-in flow. Complete any Discord approval or security check yourself; never share your password or a login code in a team chat.
Open your profile settings
Select your name/avatar, then Edit profile or Profile settings. Fill in your public display name, bio, simulations and racing details. Review which details you want other people to see.
Check Discord identity
In profile settings, open Discord identity. If it is not connected, use Connect Discord. If the wrong account was used or the link no longer works, reconnect the intended account.
Check the setup journey
The Discord Bot page checks your account, team, server connection, permissions and first race entry. Follow incomplete steps instead of creating another account or another team.
Build your driver profile#
Your driver page is more than a racing card: it is a public profile with a banner, avatar, timeline, photos and lap records.
Make it yours
Open your own profile and use the appearance controls to upload a banner or avatar. You can also use one of your own timeline photos as your avatar. Without a custom picture, your Discord avatar remains the fallback.
Set your racing identity
In Profile settings, add your bio, simulations, preferred classes/cars and main team. The main-team choice controls your public team association; it is not an upload of a separate team logo. Team managers maintain the team logo.
Share a race moment
Use the timeline composer for a post, up to four race screenshots, or a personal lap record. Review the public-publication acknowledgement before publishing. Upload only images you have the right to share.
Control your wall
You can allow or disable guest wall posts. Authors, profile owners and site moderators can remove content. Use Report for content that breaks the community rules; comments are separate from the guest-post switch.
Choose your driver number#
Give your name a recognisable racing number. It appears on your profile and on the image-native Discord race card beside your driver name.
Open the number editor
Go to Profile settings and find the personal driver-number editor. Choose a number from 0 to 999 — at most three digits.
Choose its appearance
Select a racing-number style and optionally one or two colours. Two colours create a diagonal gradient. Check the preview before saving.
Respect team availability
A number cannot be used twice within the same team. If it is taken, choose another available number. Separate teams can use the same numbers.
Let the fallback help
Drivers who have not chosen a number receive a persistent random number. Team conflicts are handled with a team-specific reservation, so a join can require a different number for that team.
Create or join a team#
The team is the home of your members, media, race entries and Discord connection. You can explore public team pages before joining.
Join an existing team
Open Teams, choose a team and use Join team where available. Write a useful introduction: simulator, preferred class, availability and experience. Managers review applications; a request is not an automatic membership.
Or create your team
Use Create team on the Teams page. Enter a name, short name and introduction, then choose a region, driven simulations and classes. Save once you are ready to create the real team.
Finish the team setup
Open Edit team to add your logo, wide banner, gallery and public links. Invite members through the team's invitation tools or review incoming applications.
Give people the right access
The owner keeps ownership; assign management or specialist permissions deliberately. A team role and an event crew role serve different purposes.
Team identity, colours & partner pages#
Your logo is part of the team's visual identity across GridUnion. The same logo-derived accent palette is used on the team page and its Discord race cards.
Upload a clear logo
In Edit team, expand the image/branding section. A square or transparent PNG works well. Use a logo that remains recognisable at small sizes.
Add a wide banner
Use a broad team image, approximately 3:1. Keep important text and the main subject away from the extreme edges because the banner adapts to the screen.
Keep gallery and tagged liveries distinct
Team gallery photos decorate the team page. To automatically put the right car on a Discord race card, upload a team livery in Liveries and tag its simulator, class and exact vehicle.
Check the result
Open the team overview and a connected race card. Without a logo, GridUnion uses a team abbreviation; without matching livery artwork, it uses a neutral car symbol.
Edit the team page without losing its identity#
Edit team keeps the public identity in one organised form. Expand the section you need instead of changing unrelated settings.
Identity & racing profile
Update the team name, short name and description at the top. Racing profile holds your region, simulations and racing classes. Keep this information useful for prospective teammates.
Logo, banner & gallery
Upload the team logo and a wide banner here. You can also add gallery photos. The Clear existing gallery option removes the previous gallery before new uploads: leave it unchecked unless that replacement is what you intend.
Public links
Add only links you want on the public team page: website, Discord invite and your social channels. Do not paste private channel links or invitation codes intended for a single person into public text.
Save and verify
Save the form, then return to Overview and Media to check the result. Discord connection, roles and race entries have their own sections; editing a banner does not require reconnecting the bot.
Members, roles & permissions#
GridUnion roles control what people can do on the website. Imported Discord roles keep their origin visible, so you can distinguish them from roles created in GridUnion.
Open Management / Edit roles
Owners and authorised managers can inspect team roles and their permissions. Use the origin labels to distinguish GridUnion roles from Discord imports.
Refresh before importing
If Discord roles have been renamed or removed, refresh the Discord role catalogue in the role-import area. Select only the roles useful for team organisation, then use the available import/synchronisation action.
Check the actual permissions
Review each imported role's website permissions and member assignments. A familiar Discord role name does not by itself grant the same authority on GridUnion.
Assign event responsibilities separately
Driver, spotter, strategist, race engineer and crew-chief assignments in a race workspace apply to that particular car entry. They do not replace team-wide membership or ownership.
Find a race & choose the correct start#
A series can have several starts. Always choose the exact occurrence you intend to enter, not just the right event name.
Filter the schedule
Open Race and narrow the list to the simulator and event type you need. Open an event for its detailed circuit layout, car classes, format and requirements.
Choose a start slot
Use Start slots / Other starts to select the correct day and time. Separate starts have separate entries and recruiting. A date window or “to be announced” notice is not a confirmed start time.
Check eligibility and source
Compare the listed licence or safety-rating requirement with your profile and the official source schedule. Simulator ownership, eligibility and registration remain the simulator's responsibility.
Share the event
Copy the URL of the exact event page. Discord can display an event preview image. Existing Discord previews may stay cached; this public link preview is separate from the interactive team race card.
Create a car entry or a custom race#
The event describes the race. A car entry describes your team's participation: vehicle, line-up, setup, stint plan and connected Discord channel.
Register an official event
On the chosen start, open Register / manage entry. Select your team, a saved line-up if available, an optional entry name and the eligible vehicle. Register entry creates the team's actual race workspace.
Create your own race when needed
On your team page, open Races and use the custom-race creation control if you have permission. Enter the simulator, event name, circuit, start and race format/duration, then the car details. Review the timezone and channel policy before saving.
Give multiple cars clear names
Create a separate entry for each car or line-up. Use meaningful names instead of relying on Car 1 / Car 2. Each entry has its own drivers, planning and Discord resources.
Review the status strip
The workspace distinguishes GridUnion registration, simulator registration, line-up confirmation and setup availability. These are different checkpoints. Mark simulator registration only after the real entry has been completed in the simulator.
Build the driver line-up & support crew#
Use one member pool instead of several long selection lists. Drivers get the main space; support roles remain separate and easy to scan.
Find a person
Open the race workspace's Line-up & crew section. Search the member pool or filter it by team role.
Assign the race role
Drag a person into Drivers, Spotters, Pitwall viewers, Strategists, Race Engineers or Crew Chiefs. On touch devices or with a keyboard, select the person and choose Assign selected instead.
Save, then confirm
Review the assignment cards and save the line-up and crew. Use the separate line-up confirmation action when the saved list is final. Discard changes returns to the saved state.
Use the right permissions
View-only support roles do not grant strategy-editing or pit-command authority. The labels describe the event responsibility; only permitted actions are enabled for your account.
Plan stints, availability & handovers#
Open Stint Planner from the car's race workspace. Drivers can volunteer; authorised team staff make the official assignments.
Check the planning assumptions
Review race duration, expected pace, fuel and tyre settings before calculating the plan. Use Save & recalculate after changing the inputs. Estimates are only as useful as the values you enter.
Offer your availability
Drivers use I am available for the stints they can drive. Availability is an offer, not a confirmed assignment. Remove it if your plans change.
Assign from either pool
Managers can use the available drivers for a stint or the full member pool, then drag a driver onto that stint. Use the selection controls when drag-and-drop is inconvenient. Review time windows and overlaps before committing.
Prepare the handover
Check the assigned driver, planned start/end, tyre choice and stops for each stint. Revisit the plan after a pace change, extra stop or driver change; a plan is not live timing or a guarantee of the next pit lap.
Review the plan before race day
Use Review & mark ready to check the current revision. A later change makes the previous review outdated, so review again. Start next stint is a race-day action: it closes the running segment at the current time and recalculates the schedule. Do not use it merely to browse the next row.
Share setups & keep race details current#
The race workspace keeps the private setup and entry status close to the driver line-up.
Upload the correct setup
An authorised team member uploads the setup in Registration / Race details. The maximum setup size is 10 MB. Make sure it matches the simulator, car and event.
Download from the workspace or Discord
Participants can download an uploaded setup from the race workspace and the connected Discord race post. No file means no download link. The link does not install the setup in your simulator.
Update rather than duplicate
Use the existing entry to change the car, line-up or setup. Review the saved result and Discord synchronisation status. Use Retry Discord Sync if an authorised account sees a failed connection.
Understand channel lifetime
The team defines race-channel naming and automatic deletion. An event can inherit that rule, override it, or keep its channels. Review the displayed policy before relying on a channel as permanent storage.
Connect the bot & configure your server#
The bot links your team's website entries with the Discord server your team actually uses. Use the setup checklist to see what is still missing.
Connect the team server
From the Discord Bot page or your team's Discord section, use Add bot & connect server. Choose the intended server and complete Discord's permission prompt. You need the appropriate server and GridUnion team authority.
Check permissions and categories
Choose where race text channels should be created. Check that the bot can see the category and perform the required channel, message and attachment actions. The setup check is preferable to blindly granting Administrator.
Choose whether you want voice channels
Automatic race voice is off for new connections. In the team's race voice settings, opt in only if wanted and select the category and any additional allowed roles. Existing teams keep their previously saved choice.
Use the schedule commands
Use /iracing for upcoming official team/special events and /lmu for LMU team/endurance events. Team class/licence filters affect the bot's schedule results, not the entire website schedule. /schedule_refresh is limited to members with Manage Server.
Read & use your team's race card#
The shared race-channel message uses a large GridUnion-rendered image with team colours, car artwork and the participating drivers. The actions underneath remain native Discord buttons.
Read the card
Check the event, team/car entry, circuit, start, duration and driver roster. Driver names use their linked Discord identity, with their GridUnion number alongside. Spotters and other supporting information use smaller sections.
Confirm or withdraw
Choose I'm driving or I'm not driving for that entry. The shared channel message is refreshed after participation changes, so everyone sees the same updated roster — it is not a separate personal card.
Open the full workspace
Use Open on GridUnion for spotting, detailed management, the complete line-up and planning. Delete event remains permission-protected. A setup download is available separately when a setup has been uploaded.
Read local time below the image
The native Discord timestamp can display the start in each viewer's timezone. A shared image cannot show different local times to different viewers at once. Its countdown updates in broader steps; it is not a second-by-second clock.
Upload liveries & match them to the right car#
Liveries is a gallery for presenting finished work, not a paint editor. Paint your car in your usual tools, then publish the artwork with the correct GridUnion tags.
Open Upload a livery
Enter a title, then select simulator → class → exact vehicle. Use the proper model rather than just typing GT3 in a description. Add a short description of the design.
Choose who it belongs to
Under Publish for, choose your team if the artwork should be used for that team's race entries. My driver profile is a personal public upload; Private is visible only to you and is never used for a public race-card image.
Upload useful views
Add a main JPG, PNG or WebP image (up to 12 MB) and optionally up to four additional views. Prefer a clean image showing the entire car. Confirm your publication rights, then publish.
Use the matching car in the race
Register that same team with the same simulator and exact vehicle. GridUnion can then select its latest matching public team livery for the Discord card. Another team's car, a private upload or a gallery image without the matching vehicle tags is not substituted.
Share your rig & discover other setups#
Show the hardware behind your racing. Rig profiles combine photos and equipment details so other drivers can find ideas and compare setups.
Open My rig
Choose Share your rig in the Rigs gallery or My rig in Profile settings. Give the setup a name and describe what makes it work for you.
Add hardware and photos
Fill in the available wheelbase, pedals and display/VR fields, then add useful pictures. Remove identifying household details or private information from photos before uploading.
Publish deliberately
Review the rig's visibility and save/publish controls. Check its public page after saving; a draft or unpublished setup does not belong in the public gallery.
Explore and give feedback
Use the gallery's hardware filters and Trending, Top Rated, Newest or Most Rated views. Rate fairly and leave constructive feedback where discussion is available.
Explore circuits, layouts & track knowledge#
A circuit page brings together the venue, available simulator layouts, pictures and upcoming races. Check the layout as carefully as the circuit name.
Open the circuit from a race
Use Circuit profile on an event, or browse the Circuits directory. Compare the event layout with the configurations listed for your simulator; similarly named configurations can be different.
Review facts and imagery
Use Layouts & facts and Gallery for an overview. Length, pit speed and available features describe the listed configuration; always follow the rules of your actual simulator session.
Find races and share knowledge
Upcoming races links to individual events at this venue. Use Comments for useful circuit observations and Rate circuit for a considered community rating. Do not enter a personal lap time as if it were a verified circuit result.
Keep personal records on your profile
Add a favourite circuit in Profile settings. Store your own lap records on your driver timeline with simulator, exact layout and car, and make clear that they are self-reported.
Find drivers, teams & specialist roles#
Connect separates people offering skills from teams recruiting. It also separates a long-term seat from help for one specific event.
Choose the right side
Browse People offering skills to find drivers and specialists, or Teams recruiting to find an open team role. Open a listing for the full requirements and contact details.
Set the scope
Choose Long-term / General for an ongoing team relationship. Use Specific event, or the event page’s Find crew area, when you need people for an exact start slot.
Narrow the match
Filter by role, simulator, class, region and language. More filters includes pace, availability, safety and voice preferences. Clear filters if the result list looks unexpectedly empty.
Publish a useful listing
Use Create listing and choose the appropriate offer or request. State the role, simulator, expected availability and relevant requirements. Keep the listing current or close it when the place is filled. A listing is not a race entry or a confirmed stint assignment.
Lap records, discussions & profile points#
Use the right place for the conversation: a driver timeline for personal race moments, circuit/event discussions for shared knowledge, and Connect for recruitment.
Record a personal lap
On your own driver timeline, add simulator, circuit/layout, car and lap time. These are self-reported personal records, not verified telemetry or an official leaderboard. Include the exact layout and conditions in your post.
Discuss the right topic
On a circuit or event page, use the relevant discussion section for braking points, setups or strategy. Keep race-slot recruiting separate from long-term team recruitment in Connect.
Like and comment meaningfully
Timeline posts, comments and received likes can contribute to profile points. Self-likes are blocked; daily limits apply. Deleted content or withdrawn likes can remove the related credit. Reposting is not a way around the limits.
Stay in the loop
Team notifications surface items such as applications and Team Principal Radio activity for permitted users. Product-update DMs are a separate opt-in: read Updates and subscribe only if you want them.
Quick fixes & what is coming next#
Start with the state shown on the live page. This guide uses snapshots, so people, dates and entries in its pictures will change.
I cannot edit a team or race
Check that you are signed in with the intended personal account, belong to the team and have the required permission. Public team pages intentionally hide private management tools.
My livery or logo is missing from the card
Check the team logo in Edit team. For the car, check the livery's publishing team, public visibility, simulator and exact vehicle tag against the car entry. Generic fallbacks appear when no valid match exists.
Discord information seems old
Check the website's saved state and sync status first. Reopen the channel; a cached image can lag behind. For stale role choices, refresh the role catalogue. For missing race results, check the command filters and known start times.
Where are the overlay instructions?
Overlays, Jeff and Pitwall are still being refined. A dedicated guide for the upcoming release will follow. This handbook deliberately focuses on the website and Discord workflow for now.