> For the complete documentation index, see [llms.txt](https://docs.revelator.com/pro/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/pro/getting-started/onboarding-to-revelator.md).

# Onboarding To Revelator

## Overview

Welcome to Revelator Pro! This guide will walk you through the key steps to onboard your catalog, activate and configure your supply chain, ingest rights and reporting data, and set up royalty splits. By following these guidelines, you will ensure a smooth and efficient onboarding experience.

Your Revelator team is here to help you at every step—whether it’s delivering your catalog, setting up your supply chain, migrating from a previous distributor, or configuring white label branding.

* **Questions?** Reach out to your Revelator Support contact.
* **Need Help with the Worksheets?** Check the Sample tabs, or ask us directly for guidance.
* **Ready to Launch?** Ensure all the DNS records, branding elements, and distribution deals are in place so that you can start using your Revelator Pro account to its fullest.

We look forward to a successful onboarding experience and supporting your growth with Revelator Pro!

## Setup Your Supply Chain  <a href="#https-app.gitbook.com-o-mempli-kwifjex2vrho-s-meiw8xrgqlp3-v0urkn-changes-185-getting-started-onboar" id="https-app.gitbook.com-o-mempli-kwifjex2vrho-s-meiw8xrgqlp3-v0urkn-changes-185-getting-started-onboar"></a>

[Migrating your Catalog](/pro/getting-started/onboarding-to-revelator/migrating-your-catalog.md)

Ingesting Your Catalogue

***

## Getting Started With Revelator

{% stepper %}
{% step %}

### Setup Your Supply Chain  <a href="#https-app.gitbook.com-o-mempli-kwifjex2vrho-s-meiw8xrgqlp3-v0urkn-changes-185-getting-started-onboar" id="https-app.gitbook.com-o-mempli-kwifjex2vrho-s-meiw8xrgqlp3-v0urkn-changes-185-getting-started-onboar"></a>

{% endstep %}

{% step %}

### Import or Migrate Your Catalog

Ensure your catalog is in our system to utilize Reporting and Royalties workflows. With integrations to major aggregators like CI, FUGA, and AudioSalad, seamlessly sync your data. If CI or FUGA aren't your partners, import metadata and assets (audio & cover art) directly.
{% endstep %}

{% step %}

### Configure Your Account Settings

{% endstep %}

{% step %}

### Setup Your Payment Preferences

Getting paid by revelator and paying your clients
{% endstep %}

{% step %}

{% endstep %}
{% endstepper %}

1.

{% hint style="info" %}
If you're a White Label customer, please follow our guide for setting up additional featues.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.revelator.com/pro/getting-started/onboarding-to-revelator.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.