Project Membership
Members are users or teams that are granted access to a project. Each member is assigned a role that define their permissions. These roles will be granted to each of the allowed clusters of the project. Only users and teams that are members of the project have access to the project's allowed clusters.
If you don't have a project, create one.
Project Roles​
There are 3 default roles available for every project.
| Name | Create New Spaces / Clusters | Access Spaces / Clusters | Create Without Template | Create With Template | Access to Project Secrets |
|---|---|---|---|---|---|
| Project admin | Yes | All Spaces and Clusters | Yes | Yes | Yes |
| Project User | Yes | Only owned and with explicit permission | No | Yes | Yes |
| Project Viewer | No | Only with explicit permission | No | No | Only in Spaces and Clusters with permission |
Global admins can change these existing roles as well as add new project roles in the Users section of the platform.
Go to Platform > Users & Roles.
In the Users page, click the Global Roles at the top. Then click the Create Role.
Fill the display name of the role and other information if necessary.
warningThe created role will be a global role by default. To create the role as a project role, add the
loft.sh/project-role: 'true'in the labels of the role resource configuration on the right side of the page.Add the project role configurationapiVersion: management.loft.sh/v1kind: ClusterRoleTemplatemetadata:name: ''labels:loft.sh/project-role: 'true'spec:management: trueClick the Create Role button at the right bottom of the page.
If you created a project role, click Project Config and find the display name of the created project role in the role selector for each member under the Members and Roles section.
Users​
Any user can be made members of a project. Follow the instructions below to add and assign roles to users, or remove them from the project.
Add users​
Select the project from the project selector, then click Project Config.
In the Members and Roles section, click .
Search for the user and select it. The user appears in the members table.
In the user's row, choose a role from the Role selector.
Click .
Instead of adding every user, select Everybody to add a wildcard member, a user named *. A wildcard member covers every identity in the project's own scope, not every identity on the platform.
- On a tenant's project, it covers that tenant's users and team access keys.
- On a project no tenant owns, it covers the platform's users and team access keys, and no tenant's.
A team named *, shown as All teams, covers the same identities. Users and teams created later are covered from their first request, without a change to the project. Use this option with caution, because every new identity in the scope gets the member's role. See Project membership.
Remove users​
Select the project from the project selector, then click Project Config.
In the Members and Roles section, click the Remove member icon in the user's row.
Click .
Teams​
Instead of assigning individual users, add a team to give all its members access to a project.
Add teams​
Select the project from the project selector, then click Project Config.
In the Members and Roles section, click .
Search for the team and select it. The team appears in the members table.
In the team's row, choose a role from the Role selector.
Click .
Remove teams​
Select the project from the project selector, then click Project Config.
In the Members and Roles section, click the Remove member icon in the team's row.
Click .