# Event Settings The **Event Settings** screen in RUFUS Race Manager allows you to configure the main properties and operational behavior of the selected event. To access it, select the **Settings** icon from the sidebar menu.

Event Settings

## General Settings Use this section to edit the basic event information: * **Name**: event name. * **Edition**: event edition or version. * **Start Date**: official event start date. * **Event Location**: location associated with the event. ## Gender Mapping Gender Mapping defines how RRM identifies and displays participant gender values in the event data grids. For example, you can map values such as `M` and `F` so participants are visually categorized in a consistent way across the interface. You can introduce two or more values sepparated by comma. ## Timekeeping The Timekeeping section defines the timing precision used by the event. Available precision options may include: * Seconds * Tenths of a second * Milliseconds Select the precision that matches the timing requirements of the race. ## Event Reference Date The Event Reference Date is used to calculate participant age. This is especially important when age groups or categories depend on the participant’s age on a specific date. ## Participant Data Style Participant Data Style controls how participant text fields are normalized when importing or editing participant records. You can configure formatting rules for fields such as: * Name * Lastname * City * Team * Club For example, you can apply capitalization rules to keep participant data consistent and easier to read. Use **Apply to Current Participants** to normalize the existing participant records using the selected formatting rules. ## Reference Table The Reference Table allows you to manage the relation between **Chip / EPC values** and **bib numbers** for the event. It is used to resolve passings, match chip reads with participants, and control chip visibility across the event interface. From this section, you can: * Review the current reference table status. * Upload a CSV reference table. * Add or edit individual rows. * Search by chip or bib. * Hide chip columns across the event UI. For more details, see the [**Reference Table**](/rufus-race-manager/collecting-and-managing-timing-data/chip-to-bib-reference-table.md) help article. ## Automatic Publication Updates Automatic Publication Updates define how a published event should refresh information in the RUFUS Events App. When enabled, RRM can automatically update selected publication areas, such as: * Participants * Results * Race progress This setting is useful when the event is published and the public-facing information must remain synchronized during the race. For more details, see the [**Automatic Publication Updates**](/rufus-race-manager/publishing-in-the-rufus-event-app/automatic-publication.md) help article. ## Notifications The Notifications section controls which passing-related alerts are shown during event operation. You can enable or disable notifications for: * **VALID passings**: passings correctly matched and accepted. * **EOTR & CLOSED passings**: passings outside the expected lap or received while a checkpoint, race, or device is closed. * **ORPHAN, NO\_RACE & WRONG\_RACE passings**: passings not matched to a participant, linked to a participant without a race, or linked to the wrong race. * **BOUNCED & TIME\_INVALID passings**: passings rejected due to bounce rules or invalid timing data. Adjust these options according to the type of information you need to monitor during the race. ## Custom Fields Custom Fields allow you to store additional participant information, such as: * Address * T-shirt size * Company * Any event-specific data field Custom fields can be displayed, filtered, and grouped in participant, segment, and result views. ## Event Status Event Status controls the visibility of the event in RUFUS Cloud and RUFUS Events App. Published events can appear in the Cloud Events Dashboard and can be made available in the RUFUS Events App. ## Danger Zone The Danger Zone contains operations that affect the entire event. Use these actions carefully. ### Export Event to File Creates a full event backup file containing the event configuration and data. This can be used for: * Backups * Moving events between systems * Archiving event data ### Clone Event Creates a copy of the current event configuration. This is useful when preparing another edition of the same race using a similar structure. ### Reset Event Clears operational event data, such as timing sessions and results, while preserving the event structure. ### Delete Event Permanently removes the event from the system. This action cannot be undone. ## Saving Changes After modifying the event settings, click **Save** to apply the changes. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.runonrufus.com/rufus-race-manager/event-management/event-settings.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.