After this article
You will be able to connect Snowflake to Lumos to sync users, roles, privileges, and usage data, and to create, update, deactivate, and delete Snowflake users and manage their role assignments.Capabilities
The connector also exposes a custom Set Default Role action.
Required plan and roles
- Snowflake plan: no minimum plan is required.
- Integration user and role: the connection authenticates as a dedicated Snowflake user (entered as API User, default
lumos_integration) and runs as the role named in Role (defaultLUMOS_INTEGRATION_ROLE) on the warehouse in Warehouse Name. Grant that role the permissions in the table below. - Credential (choose one):
- Key pair: an RSA key pair that Lumos generates for you in the connection form (Get Key). You register the public key on the Snowflake integration user; the private key is created and stored with the connection.
- PAT: a Snowflake programmatic access token.
Without the provisioning grants and
ACCOUNTADMIN, the connection still validates and syncs, but write actions fail. ACCOUNTADMIN is a system role, not an account privilege; see the warning in Phase 1 before you grant it.
Read-only access vs provisioning
Is read-only possible? Yes. Granting the integration role only theSNOWFLAKE.USAGE_VIEWER and SNOWFLAKE.SECURITY_VIEWER database roles lets the connection validate and sync users, roles, privileges, and usage data with no write access. Without the additional provisioning grants the connection still validates and syncs, and write actions fail.
What read-only requires. The integration role (default LUMOS_INTEGRATION_ROLE) granted the SNOWFLAKE.USAGE_VIEWER and SNOWFLAKE.SECURITY_VIEWER database roles only, plus either an RSA key pair generated with Get Key or a Snowflake programmatic access token. Follow the steps below and stop after the sync-only grants.
What full provisioning requires. The same role additionally granted the CREATE USER and MANAGE GRANTS account privileges and the ACCOUNTADMIN role. With those grants the connector can create, update, deactivate, and delete users and manage role assignments, using the same key pair or PAT credential you already configured.
Watch out for. On a read-only connection, a role limited to the two account-usage database roles does not receive the disabled flag for the users it lists, so every account syncs into Lumos as Active, including users who are disabled in Snowflake. Read the troubleshooting note below before you rely on a read-only connection for Access Reviews. Changing the warehouse on an existing connection registers as a new integration rather than updating the current one, because the integration identity is derived from warehouse plus account. Automated deprovisioning skips Snowflake accounts with a NULL email, so populate the email attribute on any user you want Lumos to deprovision automatically. A PAT that is expired or disabled is rejected at connect time.
Instructions
Phase 1: Prepare Snowflake- Log in to your Snowflake account at
https://your-account-identifier.snowflakecomputing.com. - Go to Projects → Workspaces (Worksheets) and click + Add New to open a new SQL worksheet.
- Run the following, step by step. For a read-only connection, skip steps 4 and 5:
- Create the credential you plan to use:
-
Key pair: in Lumos, open the Snowflake Provisioning (Multi-Auth) card (see Phase 2, step 1) and choose the key-pair credential. In the Key Identifier field, enter an identifier of your choice, select Generate new keys, even if keys exist already, and click Get Key. Keep the card open, since you finish connecting in Phase 2. Copy the public key and register it on the integration user:
The script creates the user as
TYPE=SERVICE, so Snowflake’s password expiry can’t block key-pair login (error 390106). -
PAT: Snowflake only lets a
TYPE=SERVICEuser use a PAT when a network policy applies to it, so set one up first that allows the Lumos outbound IPs, as in Phase 2 of Snowflake PAT. If your account enforces an authentication policy, it must also permitPROGRAMMATIC_ACCESS_TOKEN. Then go to Governance & Security → Users, open theLUMOS_INTEGRATION_USERaccount, and scroll to Programmatic access tokens. Click Generate New Token, name it, selectLUMOS_INTEGRATION_ROLE, and click Generate. Copy the token. Tokens expire in 15 days by default, so choose a longer expiry when you generate it (or raise the limit with aPAT_POLICY), or the connection stops syncing when the token lapses.
-
Key pair: in Lumos, open the Snowflake Provisioning (Multi-Auth) card (see Phase 2, step 1) and choose the key-pair credential. In the Key Identifier field, enter an identifier of your choice, select Generate new keys, even if keys exist already, and click Get Key. Keep the card open, since you finish connecting in Phase 2. Copy the public key and register it on the integration user:
- Note your account identifier and the name of the warehouse the integration should use. The account identifier is the part of your Snowflake URL before
.snowflakecomputing.com. Forhttps://your-account-identifier.snowflakecomputing.com, it’syour-account-identifier.
- Go to Settings → Integrations → Snowflake Provisioning (Multi-Auth) and click Connect (reconnect an existing card or add a new one).
- Enter the Account Identifier, API User (the integration user’s login name, for example
lumos_integration), Warehouse Name, and Role. - Choose the credential path. For a key pair, generate it with Get Key before you submit. For a PAT, paste the token.
- Click Connect.
API Endpoints Used
Troubleshooting
PAT credential is rejected. Lumos decodes the token and fails on anEXPIRED or DISABLED state. Generate a fresh, active programmatic access token and reconnect.
Key-pair connect fails with “Invalid private key: could not decode base64 data”, or Snowflake rejects the public key with “Invalid Public key”. Connections attempted before 18 September 2026 generated an OpenSSH-format key pair that Snowflake does not accept. Reconnect the card and generate a fresh pair with Get Key; the pair is now produced in the PKCS#8 PEM format Snowflake expects.
Connected, but write actions fail. The integration role is missing provisioning grants. Grant it CREATE USER and MANAGE GRANTS, plus the ACCOUNTADMIN role for Deactivate and Delete, then retry. Sync works with only the USAGE_VIEWER and SECURITY_VIEWER database roles.
Automated removals never dispatch. The Lumos matched-account safety check rejects Snowflake accounts it cannot validate against a user. Accounts with a NULL email (common for service or ghost users) are skipped. Populate the email attribute on Snowflake users you want Lumos to deprovision automatically.
Changing the warehouse when reconnecting has unexpected behaviour. Reconnection should only be used to update credentials, avoid specifying a different warehouse or environment when reconnecting the snowflake integration.
On a read-only connection, every user syncs as Active. Lumos lists accounts with a SHOW USERS query and marks an account Suspended only when Snowflake reports that account as disabled. Anything else becomes Active. A role holding only the SNOWFLAKE.USAGE_VIEWER and SNOWFLAKE.SECURITY_VIEWER database roles does not receive the disabled flag for the users it lists, so the value arrives empty and every account lands in Lumos as Active, including users who are disabled in Snowflake. Access Reviews show disabled users as Active, so confirm a user’s real status in Snowflake before acting on a review. Granting the role the provisioning privileges described above restores accurate status alongside write access.
On a read-only connection, accounts are missing email, first name, or last name. Snowflake masks these fields for roles without MANAGE GRANTS. Because the read-only role holds SNOWFLAKE.SECURITY_VIEWER, Lumos fills them in from Snowflake’s ACCOUNT_USAGE data, which can lag up to 120 minutes behind changes in Snowflake. Wait for the next sync, or grant MANAGE GRANTS for live values.