Humanitec allows developers in your team or from across your organization to collaborate on Apps. Users can be invited to join an Organization in Humanitec. They can sign in using their existing GitHub or Google accounts. Users can work on specific Apps with permissions to perform certain actions such as Deploy to Production based on Roles that are granted by Organization Administrators and Managers.
An Organization Administrator or Manager (see Organization Roles) can invite new users to join an existing Organization in Humanitec. An invitation involves sending an email that contains a one-time link that the invited User can follow to associate either their GitHub or Google account with the Organization in Humanitec. The link will expire after 24 hours. If the link has expired before a User has accepted the invite, a new invite can be sent.
Users can be invited to an existing Organization from the Organization Settings. Note that only Organization Administrators and Managers can invite users.
Select the Organization Members tab.
Add the email address of the User you want to invite and click on Send invite.
Humanitec uses Roles to assign privileges to Users. Roles encapsulate the granular permissions that a User will need in order to perform certain tasks.
Each User can have Roles in specific Organizations, Applications, and Environment Types.
A User with the Developer Role is able to update the configuration for an App the User has access to. But the User cannot delete the App.
A User with the Viewer Role will not be able to make updates to the configuration.
Organization Roles cover permissions that affect the entire Organization in Humanitec. This includes User Management, API Tokens, Images, Resources, and Apps.
Can access Apps they have a Role for.
Can add and list Image Builds and retrieve credentials for the hosted registry in Humanitec.
Same as Member and Artifact Contributor Roles. In addition, can invite and remove Users from the Organization in Humanitec, issue API Tokens, and create Apps.
Has full access to everything within the Organization in Humanitec.
The User who originally created the Organization will have the Administrator Role by default.
There must always be at least one User in the Organization with the Administrator Role.
The Administrator is the only Role that can update Resources.
Application Roles cover permissions that affect a specific App. Application Roles can be managed in the App Settings Screen. Note that only Organization Administrators and Managers can grant Application Roles.
Has read-only access to the App.
Can update Configuration, Shared Values and Secrets, and create Environments.
Same as the Developer Role, but can additionally invite and remove Users from the App and delete the App.
The User who originally created the App will have the Owner Role by default.
Developer and Owner Roles can only create Environments with the Environment Type they have the Deployer Role for.
An Owner will not be able to delete an App unless they have the Deployer Role for all the Environment Types used in the App.
At this time, there is only one Role for Environment Types.
If a User has the Developer or Owner Role of an App, they can create, deploy, and delete Environments of this Environment Type.
All Users have the Deployer Role for the default Environment Type development.
To make managing Users easier, Administrators can specify Default Roles that are given to all Users in the Organization.
The initial settings for new Organizations are as follows:
Users who join an Organization will have the following Roles:
Manager in that Organization,
Developer in all Apps, and
Deployer for the Environment Type development.
When a new App is created:
all Users have the role of Developer for that App.
The Default Roles for the whole Organization can be changed by the Organization Administrators.