Super App as a Service has established a user management and permission control system to meet the management needs of internal mini program business and third-party ecosystem cooperation within the enterprise.
Preparations
Before you get started, it is necessary for you to understand the following concepts.
User: An individual who uses Super App as a Service and has a login account.
Team: An organization within the enterprise, such as a department, virtual project group, or third-party partner, established to achieve specific business objectives.
Role: A description of the responsibilities and permissions of team members.
Relationship analysis
After understanding the concepts of user, team, and role, you need to know the relationships among them:
1. User
Description: An individual with a login account for Super App as a Service.
Relationship: Can join one or more teams and can be a team admin.
2. Team:
Description: A department, virtual project group, or third-party partner within the enterprise.
Relationship: Involves diverse roles. Several users can join a team, with one user acting as the team admin.
3. Role:
Description: Defines the responsibilities and permissions of team members, such as a developer role having permissions to develop mini programs and submit code.
Relationship: Belongs to a team and is assumed by users.
Process illustration: User Join a team > Team Include > Role
For example:
User John Smith has a login account for Super App as a Service.
John can join the Mini Program Development Team.
Within this team, John Smith may take on the role of mini program developer, which defines his responsibilities and permissions within the team.
Note：
Only ordinary users can join teams. Super admin and platform admins can create teams but cannot join or interfere with team operations.