Create groups for access

Create account groups, add the users who need the same access, and assign each group to the workspaces where it works. Grant workspace access and Unity Catalog privileges to groups instead of to individual users, so that membership changes don't require a grant change. Create groups after you add users, because a group can only contain identities that already exist in your account.

Account groups are the primary groups for managing access. You create them in the account console or sync them from your identity provider (IdP). Workspace-local groups are legacy groups that exist in one workspace only. Databricks also creates system groups in every workspace. See Groups.

Requirements

Before you begin, meet these requirements:

Create a group and add members

Create a group in the account console and add its members. You can also add members to a group that already exists.

Create the group

Create the group in the account console, and give it a name that describes the access it grants:

  1. As an account admin, log in to the account console.
  2. In the sidebar, click User management.
  3. On the Groups tab, click Add group.
  4. Enter a name for the group, such as data-engineers or dev-ws-admins, and then click Confirm.
  5. When prompted, add the users to the group.

Group names must be unique in your account. If a group with the same name already exists, choose a different name.

Add members to an existing group

Change the members of a group that already exists in your account:

  1. On the Groups tab, select the group.
  2. Click Add members.
  3. Search for the users you want to add, select them, and then click Add.

Membership changes can take a few minutes to reach all systems.

Assign a group to a workspace

Group members gain workspace access after you assign the group to that workspace. Assigning a group gives its members access to the workspace, and any permission grants on objects in the workspace apply to the group.

Assign workspace access

Select the workspace and assign the group:

  1. As an account admin, log in to the account console.
  2. In the sidebar, click Workspaces.
  3. Click the workspace name.
  4. On the Permissions tab, click Add permissions.
  5. Search for and select the group, assign workspace entitlements, and then click Save.

Sync groups from your identity provider

Instead of creating and maintaining groups by hand, sync them from your IdP. You can use automatic identity management or a System for Cross-domain Identity Management (SCIM) provisioning connector. With Microsoft Entra ID, automatic identity management also syncs nested groups. See Automatic identity management and Sync users and groups from Microsoft Entra ID using SCIM.

Configure group sync in Microsoft Entra ID. See Configure SCIM provisioning using Microsoft Entra ID (Azure Active Directory).

If you already set up SCIM for users, groups use the same connector. Synced groups appear on the Groups tab in the account console, with the source External.

By default, you can't change the membership of an external group in the account console, because the IdP is the source of record for it. Change the membership in your IdP instead.

Verify the groups

Check each group's members, and confirm that the groups are assigned to the workspaces that use them.

Check the group's members and workspace assignment:

  1. In the account console, click User management, and then open the Groups tab.
  2. Open each group, and confirm that it has the right members.
  3. In the account console, open the workspace where the group is used, and confirm on its Permissions tab that the group is assigned.

Troubleshooting

Use these entries when a group doesn't appear in a workspace, can't be changed, or can't be used for access control.

Workspace-local groups can't be used in Unity Catalog

You can use workspace-local groups only in the workspace where you created them. You can't assign them to other workspaces, grant them access to data in a Unity Catalog metastore, or grant them account-level roles. Databricks recommends account groups instead. If you have workspace-local groups, convert them to account groups before you grant Unity Catalog privileges. See Migrate workspace-local groups to account groups.

The group doesn't appear in a workspace

An account group must be assigned to a workspace before its members can use that workspace. Assign the group on the workspace's Permissions tab, as described in Assign a group to a workspace.

You can't add a user to a group

The user must be in your account before you can add them to a group. Check that the user appears on the Users tab under User management. If not, add the user first. See Add users to your Azure Databricks account.

Groups or members are missing after a SCIM sync

Check that the groups are assigned to the SCIM application in your IdP, because unassigned groups aren't provisioned. If a group is assigned and still missing, check the SCIM provisioning logs in your IdP for errors.

With the Microsoft Entra ID SCIM connector, only the immediate members of an assigned group are provisioned, and nested groups aren't synced. Assign each group that contains users who need access, or use automatic identity management, which syncs nested groups. See Configure SCIM provisioning using Microsoft Entra ID (Azure Active Directory).

Next steps

Resource Description
Assign a group as the metastore admin Assign a group to administer your metastore independently of individual users
Groups Learn about group sources, system groups, and the Assume permission