Feature Permission Management Introduction
Feature Introduction
This document mainly introduces the management of minigame project members.
Project members: Refers to members involved in minigame development and operation who can log in to the minigame management backend, including operators, developers, and data analysts. Administrators can add or remove project members in "Member Management" and set project members' roles.
Member Management entry: OpenPaaS backend - Management - User Management - Member Management
Project member permission descriptions:
| Permission | Operator | Developer | Data Analyst |
|---|---|---|---|
| Log in to OpenPaaS platform | √ | √ | √ |
| Open capabilities | - | √ | - |
| Basic data analysis | - | - | √ |
| Version publishing and other management operations | √ | - | - |
To meet the needs of modular division of labor and sensitive information isolation in game operations, the platform has added the "Feature Permission Management" feature, which allows further configuration of project members' permissions.
Configuration entry: Management - Member Management - Project Members - Feature Permission Management:
The feature permission administrator can access any page on the OpenPaaS platform and can set project members' access permissions.
Two role identities are launched in the first phase: Monetization / Violation Handling
- Monetization access: All features related to revenue and business strategy, such as virtual payment, RTA delivery, CPS cooperation, one-package multi-distribution, revenue analysis, monetization toolbox, etc.
- Violation handling access: Features that require submission for re-review due to violations, such as violation records, entity credit score, account appeals, etc.
If the logged-in account does not have the corresponding permission, access to the relevant page will be blocked. In this case, the feature permission administrator needs to enable the permission configuration for it.