Mockoon Cloud uses a roles and permissions system to manage access to resources and actions within the platform.
Mockoon Cloud has a team-based architecture, where each team has a set of roles that define what actions users can perform within the team. Some roles have access to resources (API mocks, instances, etc.), while others do not.
Roles with resources access:
Roles without resources access:
💡 Roles without resources access do not count against the number of seats in the team and are not included in the billing.
Permissions are the actions that can be performed on resources within the Mockoon Cloud platform. Each role has a set of permissions that define what actions users can perform within the team.
Owner | User | Team admin | Billing | |
---|---|---|---|---|
Max users with role | 1 | Unlimited | 1 | 1 |
Count against the number of seats | ||||
Resources access | ||||
Access the web app | ||||
Manage cloud mock APIs (create, update, delete) | ||||
Manage deployed instances (create, update, delete) | ||||
Generate templates with the assistants | ||||
Team management | ||||
View team members | ||||
Manage team members (add/remove) | ||||
Subscription and billing | ||||
Manage subscription (view invoices, upgrade, cancel) Manage your subscription through our payment provider's customer portal |
Currently, the subscription and billing management is done through our payment provider's customer portal (Paddle). The Owner, Team admin and Billing roles can access the customer portal to manage the subscription, view invoices, or cancel the subscription.
💡When adding a Billing or Team admin role to a team, the email address registered with the payment provider to which invoices are sent will automatically be updated to the email address of the user with the new role. The customer portal will still be accessible to all users with the Owner, Team admin, or Billing roles.