Skip to content
dbeaver-devops edited this page Oct 1, 2025 · 21 revisions

Table of contents

The CloudBeaver provides a team management feature, allowing administrators to create and manage teams. This feature is integral for organizing users into groups and controlling their access to various databases.

Teams can also be linked to external identity providers, enabling automatic user assignment based on group information received during login.

Team creation

To create a new team, follow these steps:

  1. Navigate to the Settings -> Administration -> Users and Teams -> Teams.
  2. Click on the + Add button.
  3. Fill in the necessary details in the provided fields.

Field Name Description Additional Info
Team ID A unique identifier for the team.
Team Name The name of the team.
Description A brief description of the team and its purpose.
Permissions Access level for team members Admin Full Access grants full access to CloudBeaver settings
Parameters For group mapping and other metadata, e.g. AWS roles See Integration with identity providers

Note: The Parameters section is available only after you configure at least one identity provider.

Predefined Team types

CloudBeaver includes two predefined Team types:

Types Description
admin Members of this Team have full administrative privileges within CloudBeaver.
user This Team is for regular users. Administrators assign access to databases (in Team Edition, access to projects) to this team.

Tip: Administrators can configure the predefined types in the Server Settings. For more information, see Initial data configuration.

User management

In the Users tab, you can manage Team memberships:

  • To add a user to the Team, click Edit, select the desired users, and then click Add.
  • To remove a user from the Team, select the user and click Delete.

Tip: One user can be a member of a multiple Teams.

Connection management

In the Connections tab, you can manage which connections are available to the Team:

  • To add connections to the Team, click Edit, choose the desired connections, and then click Add.
  • To remove connections from the Team, select the connection and click Delete.

Updating Team memberships

For the changes to take effect, especially in cases where group memberships are updated:

  • Users may need to log off and log back in through the Single Sign-On (SSO).
  • Alternatively, users can wait for the session to timeout.

These actions ensure that the updated claims from the identity provider are received by CloudBeaver, thereby refreshing the Team memberships.

Troubleshooting mismatches

If users aren't assigned to a Team after login, check the following:

  • Incorrect group ID: The value in Team parameters must exactly match the one sent in the token. Display names usually won’t work—use raw IDs (e.g., UUID, ARN).
  • Wrong attribute name: Make sure the identity provider is configured to include the correct attribute (e.g., groups, roles) in the token.
  • Missing group claim: Some providers don’t send group claims by default. You may need to explicitly add them in the provider settings.
  • Group limit: Azure AD and some other providers may limit the number of groups included in the token (e.g., 150). Users beyond the limit won’t be mapped.
  • Session not refreshed: Changes in group membership take effect only after the user logs out and logs in again (or after session timeout).

CloudBeaver Documentation

Clone this wiki locally