Skip to main content

Add users to your Databricks account

Add the people who use Databricks to your account, and give them access to the workspaces that they need. Databricks manages users, service principals, and groups centrally at the account level, so you add each identity one time and then assign it to any workspace in the account. Add users before you load data, so that you can grant access to data through groups in later sections.

This model is called identity federation. All new workspaces use it by default. See Manage users, service principals, and groups.

Choose how to add users​

Databricks recommends that you sync users and groups from your identity provider (IdP), so that your IdP is the source of record for user accounts and group membership. Use the following table to choose a method:

Method

Use case

Automatic identity management

Identity providers that support automatic identity management. Recommended method

System for Cross-domain Identity Management (SCIM) provisioning

Identity providers without automatic identity management support

Account console

A few users added before IdP sync, such as the first account admins and workspace admins

Method

Use case

Automatic identity management

Identity providers that support automatic identity management. Recommended method

System for Cross-domain Identity Management (SCIM) provisioning

Identity providers without automatic identity management support

Account console

A few users added before IdP sync, such as the first account admins and workspace admins

Automatic identity management supports Microsoft Entra ID and Okta. See Automatic identity management.

If you use SCIM provisioning, sync users and groups to your Databricks account rather than to individual workspaces. One account-level SCIM application keeps identities consistent across all workspaces in the account. See Sync users and groups from your identity provider using SCIM.

Requirements​

You must be an account admin to add users in the account console or configure SCIM.

Add a user in the account console​

To add a user to your Databricks account without giving them access to a workspace, do the following:

Add the user​

Enter the user's details in the account console:

  1. As an account admin, log in to the account console.
  2. In the sidebar, click User management.
  3. On the Users tab, click Add user.
  4. Enter a name and email address for the user.
  5. Click Add user.

A user in a Databricks account doesn't have access to any workspace, data, or compute resources until you grant it. See Manage Databricks users.

To verify the user, go to User management > Users and check that each new user is in the list with the right email address.

Set up SCIM provisioning​

Set up account-level SCIM provisioning if your IdP can't use automatic identity management. Check the requirements first, and then generate a token for your IdP.

Requirements​

Before you begin, meet these requirements:

  • Your Databricks account must be on the Premium plan or above, and you must be an account admin.
  • You must have admin access to your IdP.
  • Your account can have up to 10,000 combined users and service principals and 5,000 groups. Accounts created on or after November 17, 2025 can have up to 50,000 combined users and service principals and 10,000 groups. See Manage users, service principals, and groups.

If your IdP supports SCIM, configure account-level SCIM provisioning so that the IdP creates, updates, and removes users in your account. The IdP steps depend on the provider, so follow the guide for your IdP: Microsoft Entra ID, Okta, or OneLogin.

Generate a SCIM token​

The token owner can be your own user or a service principal. Generate the token in the account console, and keep it until you enter it in your IdP:

  1. As an account admin, log in to the account console.
  2. Click Security.
  3. Click the Identity provider setup tab.
  4. Next to Identity provider sync (SCIM), click Generate a SCIM token.
  5. (Optional) In Select owning principal, select a service principal that is an account admin to own the token. To own the token yourself, leave the field blank.
  6. Click Generate new token.

Enter the values in your IdP​

Connect your IdP's SCIM connector to your account:

  1. Copy the SCIM token and the Account SCIM URL that Databricks displays.
  2. In your IdP's SCIM connector, enter the SCIM URL as the SAML provisioning URL, and the SCIM token as the provisioning API token. Field names vary by IdP, so follow your IdP's guide for the exact fields.
  3. Follow your IdP's guide to assign users to the SCIM application.

Databricks recommends that, after you configure SCIM, you allow all users in your IdP to access the account. See Enable all identity provider users to access Databricks.

To verify the sync, go to User management > Users in the account console, and check that the synced users have the right email addresses and display names. In your IdP, confirm that the SCIM application reports a successful provisioning status.

Assign users and groups to workspaces​

To work in a workspace, a user must be assigned to it, either directly or through a group. To assign a user or group to a workspace, do the following:

Assign workspace access​

Select the workspace and assign the user or 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 user or group, assign workspace entitlements, and then click Save.

To verify the assignment, open the workspace in the account console, and confirm on its Permissions tab that the user or group is assigned.

Identity best practices​

Databricks recommends the following practices when you add users:

  • Assign access to groups: Assign workspace access and Unity Catalog privileges to groups instead of to individual users. Group members inherit the permissions that are granted to the group. See Groups.
  • Use one source of record: After you configure IdP sync, manage users and group membership in your IdP instead of in the account console.
  • Use service principals for production: Run production jobs with service principals, so that interactive users don't need write privileges in production. See Service principals.
  • Limit admin roles: Assign the account admin and workspace admin roles to a limited number of users.

See Identity best practices.

Troubleshooting​

Use these entries to resolve account console and SCIM provisioning issues, and to manage changes to tokens, connectors, and users.

The user already exists in the account

Before you add a user by hand, search the Users tab for the email address. A previous admin may have added the person already, or a SCIM sync may have created the account. If you add a SCIM user whose email address matches an existing account user, the two accounts are merged.

Users don't appear after the sync

Check the SCIM application's provisioning logs in your IdP for errors. Common causes are an expired or wrong SCIM token, the wrong SCIM URL, or a user who isn't assigned to the SCIM application.

You rotate the SCIM token

To rotate the token, click Manage next to Identity provider sync (SCIM), and then click Generate new token. The previous token works for 24 hours, so update your SCIM application with the new token within that time.

Users were added by hand before you turned on SCIM

Account-level SCIM matches an existing account user that has the same username (email address), and merges the two accounts. Use the same email address for each person in your IdP as in your account, so that the accounts merge instead of duplicating.

Workspace-level SCIM connectors are still running

If you already provision users directly to workspaces with SCIM, turn off those connectors before you rely on the account-level connector. Don't remove users from the workspace connectors before you shut them down, because removing a user deactivates that user in the workspace.

You remove a user from the SCIM connector

Removing a user from the account-level SCIM connector deactivates that user in the account and in all of their workspaces. Removing a group deactivates its users from the account and their workspaces unless another group or a direct assignment grants them access to the account-level SCIM connector.

Next steps​