# Page Access Permission Management

This document describes how a primary account controls which Astraflow feature pages a sub-account can access.

Page access permissions are used to control which feature pages a sub-account can enter. They are configured separately from data permissions and both must be satisfied:

- **Page Access Permission**: Determines whether a sub-account can enter the corresponding page.
- **Data Permission**: Determines which data the sub-account can view and operate after entering the page. Currently applicable only to API Key Management, Model Logs, and Model Monitoring. See [Sub-Account Data Permission Management](sub-account-data-permission.md) for details.

Existing sub-accounts retain full page access permissions by default and do not need to be reconfigured. New sub-accounts need both page access permissions and the corresponding data permissions configured to access and operate the corresponding features.

## Page Permission Description

To restrict the pages a sub-account can access, grant only the target page's corresponding Action:

| Page | Permission Action |
|------|-------------------|
| SkillLab | ``` uai_modelverse:CheckMenuSkillLab ``` |
| CodeBox | ``` uai_modelverse:CheckMenuCodeBox ``` |
| Sandbox Site | ``` uai_modelverse:CheckMenuSandboxSite ``` |
| RAG | ``` uai_modelverse:CheckMenuRAGView ``` |
| Model Logs | ``` uai_modelverse:CheckMenuModelLog ``` |
| Model Monitoring | ``` uai_modelverse:CheckMenuModelMonitor ``` |
| BYOK Key Hosting | ``` uai_modelverse:CheckMenuBYOKKey ``` |
| Consumer Center | ``` uai_modelverse:CheckMenuConsumer ``` |
| API Key Management | ``` uai_modelverse:CheckMenuAPIKey ``` |
| Export Records | ``` uai_modelverse:CheckMenuExportRecord ``` |
| Recharge Card | ``` uai_modelverse:CheckMenuRechargeCard ``` |

## Configuration Steps

**Step 1**: In the Astraflow console, click **Account and Permission Management** in the account menu at the top right.

Enter the policy editing page, add a custom policy, select project-level, and add an authorization statement.



**Step 2**: When adding the authorization statement, select UAIModelverse, and choose Allow or Deny for menu display.



**Step 3**: Under the query function, filter by CheckMenu to see the Actions that control menu items, check the corresponding Actions, save the policy, and then assign the policy to the user.



## Configuration Example

To only allow a sub-account to access "API Key Management" and "Model Logs", you can directly paste the following via **Script Edit**:

```plain
{
  "Version": "1",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "uai_modelverse:CheckMenuAPIKey",
        "uai_modelverse:CheckMenuModelLog"
      ],
      "Resource": [
        "*"
      ],
      "Condition": {}
    }
  ]
}
```
