Predefined roles

The API Hub for Contract Testing tenant user will be assigned the Administrator role. They can then assign the Administrator role to other users.

All new users are assigned the User role (unless the default role has been updated in the system preferences). The User role is intended to work in conjunction with team assignments, and therefore has manage:team permissions (rather than manage:* permissions) for all resources that can be associated with a team. The User role should be assigned to all developers, testers and other users who create and verify contracts on the API Hub for Contract Testing platform.

This is the default role associated with a system account.

This role is automatically assigned to any user who is an administrator of a specific team. This role may not be edited or deleted and cannot be assigned directly via the user roles APIs or UIs.

A user with the guest role can only view contract related data through the UI and has no API access.

The guest role permissions may not be modified.

A user with the SwaggerHub role can provide an API Token for the API Hub for Design integration. This allows API Hub for Design to verify published pacts against live OpenAPI descriptions.

The SwaggerHub role permissions may not be modified.

For the System Account used by the API Hub for Contract Testing SCIM API.

The SCIM role permissions may not be modified.

The Test Maintainer role has been replaced by the User role. The difference between the User and Test Maintainer roles is that the User role has team scoped permissions for Webhook and Secret management.

Should you wish to reset the permissions assigned to each of the predefined roles back to their defaults as documented above (or upgrade from the globally scoped User role to the team scoped User role) you can follow these steps. Note that any custom roles will remain unaffected, and user/role assignments are unchanged.