# Royalty Levels **Overview** Go to **CAS** --> **Management** --> **Transaction Codes** --> **Royalty Levels** The user provides the name of the person or company with the product royalty rights, and assigns a royalty percentage for every product sold. **Details** ![](https://1065618780-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LlIO4qyICYYVdwt64xd%2F-LwqbsK1gPXh1u9VdZn6%2F-LwqceTcj7eH06q7iRW5%2F2019-12-24%2012_10_02-Window.png?alt=media\&token=86da9911-edca-4e48-82f1-807ef1a26201) Each Royalty Structure must have its own unique **Name***.* This will show up in all reports and tax filters so you should name them carefully. If you try to create a royalty structure with an existing name a popup will displayed asking you to confirm this activity. It is not advisable to create structures with the same name. This will lead to much confusion when reviewing reports. Enter the **Rate** as a percentage of what the royalty will be. Click on Save to create the Royalty Structure. **Access** Access to this function at an enterprise level is limited by default to the System Administrator and Financial users only. Accounting may modify royalty level settings at Venues or Store assigned to them. --- # Agent Instructions: 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: ``` GET https://retailcloud.gitbook.io/portals/central-administration-server-cas/untitled-1/transaction-codes/untitled-4.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.