# 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="/files/ebTMrzcsRrDlXh4WYAkm" alt=""><figcaption></figcaption></figure>

**RWA Fund Workflow Example**:

<figure><img src="/files/p9l2XaVKoghnPjgm1C7n" alt=""><figcaption></figcaption></figure>


---

# 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://docs.blockrock.win/permission-management-smart-contracts-and-audits/permission-management.md?ask=<question>
```

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.