> 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/platform/catalog/tracks/rights.md).

# Rights

### Rights Management

The Rights section in the Revelator platform allows users to view and manage both **Master** and **Publishing** rights associated with a track or asset.

### Master Rights

Master rights define the ownership and distribution of royalties generated from the recording of a track.

**Key Features**

* **Royalty Token**: Indicates that the track has a royalty token and the royalties are paid according to the token splits defined on-chain.
* **Right Holder**: Displays the entity holding the right, with token split percentages and wallet addresses.

**How to View Master Rights**

1. Navigate to the **Catalog** and select a track.
2. Go to the **Rights** tab.
3. Click on **Master** to view the distribution details, including token splits and right holders.
4. Click **Go to Royalty Token** for detailed on-chain token information.

**Verification**

* You should see a list of right holders along with their corresponding token addresses and split percentages.

### Publishing Rights

Publishing rights manage the songwriting and compositional aspects of a track.

**Key Features**

* **Writer Role**: Specifies the contribution of each writer (Composer, Lyricist, Arranger).
* **Publishing Information**: Indicates whether the work is under copyright control (self-published).
* **Shares %**: Shows the ownership percentage for each contributor.

**How to View Publishing Rights**

1. Select the **Publishing** tab within the **Rights** section.
2. Review the list of writers, their roles, and publishing information.
3. Confirm the **Shares %** for each writer.

**Verification**

* The displayed data should include accurate roles and shares for each contributor.


---

# 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/pro/platform/catalog/tracks/rights.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.