3443afdc398ce6ca4814fda68a8f2197e834aef8
wiki/racecommittee-app-administrator.md
| ... | ... | @@ -26,4 +26,14 @@ Repeat until you've configured all your devices. |
| 26 | 26 | |
| 27 | 27 | ## Configuration of devices |
| 28 | 28 | |
| 29 | -There are several preferences you can configure to control the overall functionality of the RaceCommittee App. All these options can be configured either via remote configuration (see above) or on the device itself. The remote configuration is fetched on selecting an event in the event selection screen. If there is a configuration stored on the server for the target device, it will overwrite the corresponding options in the device's local configuration. |
|
| ... | ... | \ No newline at end of file |
| 0 | +There are several preferences you can configure to control the overall functionality of the RaceCommittee App. All these options can be configured either via remote configuration (see above) or on the device itself. The remote configuration is fetched on selecting an event in the event selection screen. If there is a configuration stored on the server for the target device, it will overwrite the corresponding options in the device's local configuration. |
|
| 1 | + |
|
| 2 | +In the following we will have a look at some of these settings. |
|
| 3 | + |
|
| 4 | +### General preferences |
|
| 5 | + |
|
| 6 | +* **Device Identifier:** See above. Used to identify the device when fetching a remote configuration. |
|
| 7 | +* **Server URL:** The server the device will talk to. On change you should reload the app. |
|
| 8 | +* **Synchronize connection settings:** See above. |
|
| 9 | +* **Managed course areas:** The user is able to logon to the configured course areas. |
|
| 10 | +* **Results recipient:** When active, the race's results (photos) will be sent to this mail. |
|
| ... | ... | \ No newline at end of file |