Environment Teams and Roles

Environment Teams and Roles

Administrators can manage team members and roles in each project environment using the Liferay Cloud Console. Each environment can have unique members, and each member can have different roles in different environments.

Invite members and assign roles with varying access levels to achieve your desired team structure in each project environment.

Inviting Team Members

Follow these steps to invite users to your environment:

  1. Navigate to a project environment.

  2. Click on Team in the environment menu.

  3. Enter the user’s email into the Email field.

  4. Click the drop-down Role menu to assign a role to the new user.

  5. Click on Send Invite.

Figure 1: Invite new team members to an environment from the Team page.

Email invitations grant users access to a single project environment. Invited users must open the invitation email and click Accept Invite.

Figure 2: Click Accept Invite to gain access to the environment

New Liferay Cloud users must create an account, while returning users can Log in using their Liferay Cloud credentials.


Any user can access the Team page to see other users in the environment and their roles, including the administrators.

Managing Team Members

Current and invited team members appear in separate tabs of the Members section. Here administrators can manage team members via the Actions button in each tab.

From the Invited tab, administrators can cancel pending environment invitations.

Figure 3: Cancel pending invitations from the Invited tab using the Actions button.

From the Current tab, administrators can change team member roles or remove a member from the environment.

Figure 4: Use the Actions button to manage current team members.

Understanding Team Roles

Roles determine a user’s access level within an environment. Liferay Cloud comes with four default user roles:

  • Owner: The sole owner of the project has the most complete access.
  • Administrator: Administrators have full control over Liferay Cloud environments and their members.
  • Contributor: Contributors can handle application management and most of the development life cycle, but they can’t manage team members or perform other administrator-exclusive actions.
  • Guest: Guests have view-only access. Guests can see what is happening in the environment, but can’t perform actions or make any changes. They only have permission to remove themselves from the environment.

Here is a list of important permissions and which team roles have them:

Permission Owner Administrator Contributor Guest
Inviting/removing members X X
Changing members’ roles X X
Enabling/disabling Support access X X
Deleting an environment X X X
Deleting a service X X
Restarting/stopping a service X
Deploying a build X
Creating, viewing, or editing secrets X X
Creating a new backup X
Uploading/downloading a backup X X
Restoring from a backup X X
Enabling/disabling auto-scaling X X
Downscaling manually X X
Changing VPN settings X