> For the complete documentation index, see [llms.txt](https://docs.revelator.com/onboarding/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revelator.com/onboarding/getting-started/master.md).

# Onboarding to Revelator

## **Welcome to Revelator**

We are excited that you have chosen Revelator to power your music business. We have put together this onboarding guide to streamline the process of onboarding your catalog, activating your supply chain, ingesting your right and reporting data as smoothly as possible.

## **Understanding your requirements**

Start by filling out the[ onboarding form](https://docs.google.com/forms/d/1mm_Ul6Fy03iinF_w-Gqmpo1E7aV7fqCccAAuOFLvUGo/viewform) to help us gather all the information we need to properly set up your account.

## **Setting up your account**

Once the above onboarding information has been provided, a link to your new Revelator account will be emailed to you**.** 

Please follow the link to the login page, enter the account email and click on Forgot Password to reset your account's password. 

We look forward to working with you! Please let us know if you have any questions by emailing [support](mailto:support@revelator.com).<br>


---

# 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.revelator.com/onboarding/getting-started/master.md?ask=<question>&goal=<endgoal>
```

`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.