Link your Databricks account
Lakemine analyzes every workspace in your account from a single install. This step signs you in at the account level so the installer can confirm your admin rights and, on the next step, list your workspaces.
Your Databricks credentials stay on your machine. Lakemine never receives them.
Installer, “Link your Databricks account” panel. Cloud dropdown, account id field with a UUID entered, the “Link account” button, and the account checks list below it.
Choose your cloud
Pick AWS, Azure, or GCP. This determines the Databricks account console host the installer signs you in against, which differs per cloud. The installer shows the host it will use beneath the dropdown.
Enter your Databricks account id
This is the Databricks account UUID, in the form
00000000-0000-0000-0000-000000000000.
Find it in your Databricks account console, under the user or account menu in the top right. It is the account id, not a workspace id and not your Lakemine account.
Sign in as an account admin
Select Link account. Your browser opens and you authenticate through your normal single sign-on and multi-factor flow. The Databricks CLI caches a short-lived, auto-refreshing token in a local profile that the installer reads.
The default is OAuth, because installing is a one-time administrative act. No long-lived secret is stored, and it works in organizations where personal access tokens are disabled. A personal access token is available as a headless fallback, passed through the environment rather than typed on a command line.
Once you return to the installer it runs one check:
| Check | Blocking | What it means |
|---|---|---|
| Account admin (can list workspaces) | Yes | You are an account admin, and the installer can enumerate the workspaces in your account. |
Why account admin is needed
Account admin is required for exactly one thing during install: signing in at the account level and listing the workspaces, so you can choose where the appliance lives.
It is not needed again afterwards. The scheduled scan runs as a dedicated service principal, never as you. See How it works.
If the check fails
“Not an account admin.” The account you signed in with does not hold account admin. Either sign in as an admin, or ask one to run the install. This is one time, and once the appliance is deployed no account admin is needed for upgrades.
“Account not found.” Check the account id is the account UUID from the account console and not a workspace id, and that the cloud you picked matches the cloud your account is on.
The browser did not open, or the sign-in did not come back. Close the browser tab and select Link account again. If your organization blocks the loopback redirect the Databricks CLI uses, use the personal access token path instead.