> For the complete documentation index, see [llms.txt](https://docs.blockrock.win/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockrock.win/permission-management-smart-contracts-and-audits/permission-management.md).

# Permission Management

To ensure security, compliance, and transparency in on-chain asset management, the BlockRock platform employs a **multi-signature authorization (Multi-Signature)** and **hierarchical access control** framework.

## **1. Multi-Signature Verification (Multi-Sig)**

* **Applicable Scenarios**: All high-sensitivity operations, including fund transfers, asset allocation changes, and smart contract upgrades.
* **Execution Process**:
  * Critical transactions require **multi-party independent authorization** (e.g., platform security officers, third-party auditors, user representatives).
  * Operations proceed only after all authorized parties complete signature verification (e.g., 3/5 signature threshold).
* **Advantages**: Eliminates single-point failure risks and prevents internal/external malicious tampering.

## **2. Hierarchical Permission Management**

* **Role Definitions**:

<table data-header-hidden><thead><tr><th width="146.046875"></th><th width="125.55078125"></th><th></th><th width="196.75"></th></tr></thead><tbody><tr><td><strong>Role Tier</strong></td><td><strong>Multi-Sig Required?</strong></td><td><strong>Permission Scope</strong></td><td><strong>Example Operations</strong></td></tr><tr><td>Super Administrator (Owner)</td><td>Yes</td><td>Global system configuration</td><td>• Upgrade smart contracts, adjust underlying protocols<br>• Set/Modify administrators and operators<br>• Transfer token ownership<br>• Modify reward tokens</td></tr><tr><td>Administrator (Admin)</td><td>Yes</td><td>Fund withdrawals and token minting</td><td>• Release subscription cycles<br>• Withdraw invested funds<br>• Mint reward tokens</td></tr><tr><td>Operator (Operators)</td><td>No</td><td>Subscription cycle creation and configuration</td><td>• Create new subscription cycles<br>• Configure cycle parameters</td></tr><tr><td>Web3 Users (Users)</td><td>No</td><td>Investment and trading</td><td>Subscribe, redeem, query holdings</td></tr></tbody></table>

* **Permission Isolation**: Each tier operates independently; cross-tier access is prohibited.

## **3. Technical Implementation Flowchart**

**Permission Management**

<figure><img src="https://2927105092-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFsX7SPcT6apGe5dDBVr6%2Fuploads%2FW2cKmnYONeKfm4bECvoz%2Fimage%20(7).png?alt=media&amp;token=986209e0-ed80-4b9d-a1ba-735ed94bebd4" alt=""><figcaption></figcaption></figure>

**RWA Fund Workflow Example**:

<figure><img src="https://2927105092-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFsX7SPcT6apGe5dDBVr6%2Fuploads%2Fk11kjZVZwZAckMue9GYm%2Fimage%20(8).png?alt=media&amp;token=d97eaa5a-7aae-4211-830e-336358777b7b" alt=""><figcaption></figcaption></figure>


---

# 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.blockrock.win/permission-management-smart-contracts-and-audits/permission-management.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.
