A team is a group of users (team members) and it can be granted access to clusters by creating cluster accounts for the team similar to cluster accounts of users.
Instead of statically assigning users to a team, you can also define "Kubernetes Groups" as team members. This is an advantage if you are using OpenID Connect for authentication because your existing team structure can be easily reflected in loft without the need to manually replicate team memberships.
Example: Your organization is working with GitHub and has existing teams with different members and access permissions in GitHub. If you configure loft to use GitHub as OpenID Connect Auth Provider and you create the teams you want to give Kubernetes access in loft, you can define a group membership for the GitHub team name. The result of this is that all users who are part of the GitHub team will also become a member of the corresponding team in loft.
The screenshot below shows the group "analytics-team" being added as member of the Analytics Team.