Team Management
Permissions are divided into two parts: team permission and project permission. Team permission determines a user’s permissions to manage the team. Project permission determines a user's level of access to an Apidog project.
Team Permission
There are three team roles: owners, admins, and users. The respective level of access to the team is as follows:
Permission Type | Owner | Admin | User |
Update team info | √ | × | × |
Handover team | √ | × | × |
Disband team | √ | × | × |
View member permission | √ | √ | × |
Update member permission | √ | √ | × |
Invite/Remove members | √ | √ | × |
Project Permission
In order to meet the different level of management needs, each member has the ability to set the roles of admins, general member, read-only member and no access member by project. The corresponding permission is as follows:
Permission Type | Admin | General Member | Read-only Member | No Access Member |
Create, delete, update project | √ | × | × | × |
Update project info | √ | × | × | × |
Access API documentation | √ | √ | √ | × |
API creation, deletion, and update | √ | √ | × | × |
API debugging | √ | √ | √ | × |
Create, delete, and update use case | √ | √ | × | × |
View and run use case | √ | √ | √ | × |
Create, delete, and update data model | √ | √ | × | × |
View data model | √ | √ | √ | × |
Create, delete, and update environment | √ | √ | × | × |
Create, delete, and update Mock rule | √ | √ | × | × |
Create, delete, and update public response | √ | √ | × | × |
Create, delete, and update public script | √ | √ | × | × |
Create, delete, and update database access | √ | √ | × | × |
Create, delete, and update custom methods | √ | √ | × | × |
Create, delete, and update variables | √ | √ | × | × |
Assign local value to variables | √ | √ | √ | × |
Import/Export data | √ | × | × | × |