User roles determine the access level or permissions of a person authorized (invited by a Harbormaster) to use the Harbormaster App.
Overview
-
Harbormaster – company administrator with full access the entire Harbormaster application.
- Release Manager – has access to create Shipping Lanes, Vessels and trigger Voyages.
- Repository Administrator – has access to restrict approve or disapprove Docker image sources and tags from Docker Hub, Docker Hub Enterprise and Private Registries.
-
Stevedore – has access to view and manage Harbors, Clusters, Engines and Containers.
-
Developer (public sites) – has access to define Containers.
-
User – general user role required by all users.
Harbormaster
A Harbormaster has full control of the entire application. Harbormasters can create more Harbormasters, add, remove, and change user roles. They have complete control over Harbors, Clusters, Engines, Shipping Lanes, Vessels, Voyages, Containers, Registries, and AWS Instances.
Release Manager
A Release Manager has container release coordination control. Release managers define the workflow for the progression of Vessels along a Voyage. This could be anything from a traditional the development, test, and production Harbor configuration through to a more complex integrations and regression testing Harbor configuration.
Repository Administrator
A Repository Administrator has image security control. Repository Administrators are the image gatekeepers; through approving or disapproving the use of Public and Private images they ensure open source and propriety images are safely deployed to Harbors.
Stevedore
A Stevedore has management control. Stevedores can view, control and report on the overarching container environment.
Developer
A Developer has container definition control. Developers can configure container instantiation parameters using images approved by Repository Administrators.User
This is a standard user role required by all users and is planned to include Break Glass functionality for emergencies etc.