Managing Participants in TMX
The Participants tab in TMX provides comprehensive tools for managing tournament participants, from initial registration through sign-in and assignment to events. This page demonstrates practical usage of the Competition Factory's Participant Governor.

The Participants tab: a searchable, sortable table of individual participants with role, sex, sign-in status, events, city/state and rating columns. The icons above the table switch between participant views; Actions holds the bulk operations.
The screenshots on this page show TMX running locally with a tournament generated by the factory's mocksEngine; every participant is a generated mock person.
Overview
Participant management in TMX includes:
- Registration - Adding new participants with required and optional information
- Import - Bulk import from a Google Sheet or a CSV/TSV file
- Sign-in - Signing participants in and out as they arrive (a matchUp's check-in is the Scheduling tab's Check-In desk)
- Search & Filter - Finding participants by various criteria
- Editing - Updating participant information
- Assignment - Adding participants to events
Factory Methods Used
The Participants feature uses these key factory methods:
Adding Participants
// Single participant: participantRole is required (ERR_MISSING_PARTICIPANT_ROLE without it)
tournamentEngine.addParticipant({
participant: {
participantType: 'INDIVIDUAL',
participantRole: 'COMPETITOR',
person: {
standardGivenName: 'John',
standardFamilyName: 'Doe',
nationalityCode: 'USA',
},
},
});
// Bulk participants
tournamentEngine.addParticipants({
participants: [/* array of participant objects */],
allowDuplicateParticipantIdPairs: false,
});
Participant Search and Retrieval
// Get all participants
const { participants } = tournamentEngine.getParticipants({
participantFilters: { participantTypes: ['INDIVIDUAL'] },
});
// Find specific participant
const { participant } = tournamentEngine.findParticipant({
participantId,
});
// Search by name
const { participants: searchable = [] } = tournamentEngine.getParticipants();
const results = searchable.filter((p) => p.participantName?.toLowerCase().includes('john doe'));
Updating Participants
// Update participant details
tournamentEngine.modifyParticipant({
participant: {
participantId,
person: {
standardGivenName: 'John',
standardFamilyName: 'Smith',
},
},
});
// Replace the person's contact list; retain any contacts the UI should keep.
tournamentEngine.modifyParticipant({
participant: {
participantId,
person: { contacts: [{ emailAddress: 'john@example.com', mobileTelephone: '+1-555-0123' }] },
},
});
Key Features
Registration Workflow

Actions → New participant opens a drawer for adding one participant: first and last name, nickname, sex, date of birth, country, mobile and email.
-
Participant Creation
- Required fields: name, participant type
- Optional fields: nationality, contact info, rankings
- Automatic ID generation
- Duplicate detection
-
Validation
- Name validation
- Contact information format checking
- Nationality code validation
- Rating/ranking validation
-
Storage
- Added to tournament record
- Available for event assignment
- Preserved across sessions
Import Options

The Actions menu on the Participants tab: import from a Google sheet or a CSV/TSV file, add a new participant, print the player list or a call sheet, edit ratings, and sign-out operations. Generate mock participants fills a tournament with generated people for testing.
Google Sheets Integration
// TMX can import directly from Google Sheets
// Uses factory's participant structure
CSV Import
// Standard CSV format
// Headers: firstName, lastName, nationality, rating, etc.
// Mapped to factory participant structure
Participant Assignment
// Assign participant to event
tournamentEngine.addEventEntries({
eventId,
participantIds: [participantId],
});
// Assign with entry status
tournamentEngine.addEventEntries({
eventId,
participantIds: [participantId],
entryStatus: 'DIRECT_ACCEPTANCE',
});
Participant Data Structure
TMX uses the standard factory participant structure:
{
participantId: 'uuid',
participantType: 'INDIVIDUAL',
participantRole: 'COMPETITOR',
person: {
personId: 'uuid',
standardGivenName: 'John',
standardFamilyName: 'Doe',
nationalityCode: 'USA',
sex: 'MALE'
},
rankings: [
{
rankingType: 'RATING',
ratingType: 'UTR',
rating: 12.5
}
],
timeItems: [
{
itemType: 'CHECK_IN',
itemValue: '2024-01-15T09:00:00Z'
}
]
}
UI Components
TMX builds this tab from these courthive-components exports:
- controlBar - the toolbar above the participants table: search, filters and the Actions menu
- renderForm and renderButtons - the add and edit participant forms
- cModal - the dialogs those forms open in
- renderParticipant - a participant as TMX's table cells show it
- buildRatingDistributionChart - the histogram of the participants' ratings in the tab header
- renderTeamColorsEditor - a team's colours
The participants table itself is a Tabulator grid in TMX's own code.
Common Patterns
Adding a New Participant
// 1. Create participant object
const participant = {
participantType: 'INDIVIDUAL',
participantRole: 'COMPETITOR',
person: {
standardGivenName: firstName,
standardFamilyName: lastName,
nationalityCode: country,
},
};
// 2. Add to tournament (returnParticipant: the result carries only { success } without it)
const result = tournamentEngine.addParticipant({ participant, returnParticipant: true });
// 3. Handle result
if (result.success) {
const { participant: added } = result;
// Update UI with new participant
}
Bulk Import Workflow
// 1. Parse import data (CSV, Sheets, etc.)
const participants = parseImportData(data);
// 2. Validate participants
const validated = participants.filter((p) => validateParticipant(p));
// 3. Add to tournament
const result = tournamentEngine.addParticipants({
participants: validated,
});
// 4. Report results: { success, addedCount }, or { error } with nothing added
if (result.error) console.error(result.error);
else console.log(`Added: ${result.addedCount}`);
Participant Check-in
// Tournament check-in is the participant's sign-in status
tournamentEngine.modifyParticipantsSignInStatus({
participantIds: [participantId],
signInState: 'SIGNED_IN', // or 'SIGNED_OUT'
});
// Query signed-in participants
const { participants: checkedIn } = tournamentEngine.getParticipants({
participantFilters: {
participantTypes: ['INDIVIDUAL'],
signInStatus: 'SIGNED_IN',
},
});
Best Practices
Data Quality
- Use factory methods to validate before invoking remote execution
Performance
- Use bulk operations for multiple participants
- Understand factory based filtering capbilities
Related Documentation
- Participant Governor - All participant-related methods
- Entries Concepts - How participants become event entries
- Participant Types - Data structure reference
Next Steps
Once participants are registered, proceed to Events & Categories to create tournament events and assign participants.