> For the complete documentation index, see [llms.txt](https://docs.napier.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.napier.finance/curate/napier-curation/manage-market/role-allocation.md).

# Role Allocation

Curators can allocate a role of their markets to one or multiple addresses via the Curator Dashboard. 

### Using the Curator App

Follow the steps below to pause their markets:

{% stepper %}
{% step %}

### Step 1: Preparation

* Access the **Curator Dashboard**.
* If your account is not verified, complete verification under **Verify Your Account**.
* If you haven’t created a market yet, follow the steps in **Create Market**.
  {% endstep %}

{% step %}

### **Step 2: Allocate a Role**

<div align="left" data-with-frame="true"><figure><img src="/files/ZqTfoB0cDQssLpEBbKTE" alt="" width="563"><figcaption></figcaption></figure></div>

Select one role from the options below.

* Owner
* Fee Collector
* Protocol pauser
* Protocol unpauser
* Rehypothecation manager
* **Developer**
* Renounce all

{% hint style="info" %}

### **Market Types**

Yield markets differ by underlying asset and use case. Depending on whether the underlying is actively governed or immutable, **selective governance** may be required. Napier classifies markets as follows:

* **Verified** — Created by a verified curator.
* **Unverified** — Created without verification.
* **Unstoppable** — Immutable market (all curator permissions renounced except Fee Collector).
* **Banned** — **F**lagged as inappropriate or malicious.
  {% endhint %}

{% hint style="info" %}
You can assign one or more roles to one or more addresses.
{% endhint %}

{% hint style="danger" %}
**Renounce** with care: it permanently relinquishes your curator (owner) rights, and afterward no one—including you and Napier core team—can take any action on the market.
{% endhint %}
{% endstep %}
{% endstepper %}


---

# 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.napier.finance/curate/napier-curation/manage-market/role-allocation.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.