> For the complete documentation index, see [llms.txt](https://docs.racemap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.racemap.com/live-tracking/share-access.md).
# Managing Access
### Add editors to specific events
Working for multiple events in parallel involves a team. To collaborate across multiple RACEMAP accounts, you can grant your teammates access to edit the event.
Follow these steps to share access:
1. Each teammate has a RACEMAP account.
2. Create the event from your account.
3. Navigate to **Advanced > Manage Access** in the event settings.
4. Under the **Add** **Editors** section, type your teammate’s username and select it from the list.
This setup lets you efficiently manage events across teams, while keeping access secure and organized.
Select a teammate to collaborate on your events.
### Child accounts
Organizations that operate RACEMAP through multiple accounts can consolidate them under one main account using the child account structure.
* One **main account** oversees all associated child accounts
* Child accounts operate independently — they set up and run events on their own
* The main account has full read/edit access to all events and settings across every child account
* Child accounts **cannot access** each other's events
* Child accounts **do not see pricing** — billing is handled entirely at the main account level
* The main account receives **one consolidated invoice** that sums up usage across all child accounts
This setup is designed for companies managing teams, franchises, or white-label operations — where central billing and oversight matter, but day-to-day event management stays distributed.
To link accounts, the main account sends a request to naming the account to be added as child.
{% hint style="info" %}
**Tracker Management:** Share access to your GPS trackers for other RACEMAP accounts e.g. when you rent the trackers. [User access to devices](/tracker-management/user-role.md)
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.racemap.com/live-tracking/share-access.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.