How to Configure Snowflake Create User

Published
Length
3 min read

Luis Felipe Dias

All posts

You run a snowflake create user workflow by holding a high-level admin role. Then you assign a default role, warehouse, and login secret to the new account. Many engineering teams rush this step to get new developers working fast. They often attach broad admin roles so queries work on the first try. Broad roles give people and apps way too many permissions across the warehouse. A single bad query or leaked key can expose or delete production tables. How the snowflake create user workflow works

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

You run a snowflake create user workflow by holding a high-level admin role. Then you assign a default role, warehouse, and login secret to the new account. Many engineering teams rush this step to get new developers working fast. They often attach broad admin roles so queries work on the first try. Broad roles give people and apps way too many permissions across the warehouse. A single bad query or leaked key can expose or delete production tables.

How the snowflake create user workflow works

Snowflake separates user identities from data permissions in its core design. A user object only holds login details like passwords, public keys, or single sign-on links. The user account itself holds zero permissions on databases, schemas, or tables. Instead, the system attaches all data permissions to role objects.

During the snowflake create user process, an admin creates the account identity first. Next, the admin links that identity to one or more specific roles. A user logs into a session and activates an assigned role to run queries. You also set a default role and a default compute warehouse for the account. This setup ensures the person or service can run queries right after logging in. Admins can also require a password change on the first login for human accounts. For automated apps, admins usually skip passwords and attach a public key instead.

Why role design matters for new accounts

Snowflake uses a role hierarchy where parent roles inherit rights from child roles. If you assign a top-level role to a new user, they inherit everything below it. Good role design splits account creation duties from data management duties. A dedicated user admin role can make accounts without reading table rows. A separate security role can then grant specific table rights to custom roles.

Teams get into trouble when they skip custom roles for new apps or analysts. Sharing one wide role across five apps makes audit logs hard to read. When a slow query spikes costs, you cannot tell which app sent it. Giving each person and service a narrow role keeps your audit trail clean. You should also review unused accounts every month and disable old identities.

User Provisioning (SCIM) + Snowflake Access Control: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

What native account roles solve and what keeps the session active

Native roles and user settings solve the problem of who can log in. They also control which schemas and tables a session can read or change. When you set up clean roles, an analyst cannot drop a billing table. Role hierarchies let large teams group permissions by job title or service type.

Still, account creation and static roles only check permissions at the table or view level. Once a user has read rights on a customer table, every row is open by default. Native user settings do not inspect individual queries in flight before they run. A permitted user can still pull a million rows of emails or card numbers. Static roles also stay active all day and night unless an admin revokes them. If an attacker steals a service key, they get full role permissions right away. Teams still need a way to inspect queries and mask sensitive fields in results.

Check database and API queries on the wire

Identity tools, roles, and network rules decide who opens a session. Setup alone cannot check what each query does or mask sensitive values in a response once a session starts. When workflows touch Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, or internal HTTP APIs, hoop.dev sits inline in the wire protocol beside those services as an open-source proxy, a sidecar for your Postgres or API. On every query an AI agent or engineer runs against production, hoop.dev decides to pass, mask, block, or hold it for human review.

Your login details and client tools stay as they are while hoop.dev guardrails refuse bad deletes or drops before they run, and hoop.dev data masking rewrites matched sensitive values in responses in memory. Furthermore, hoop.dev holds SOC 2 Type II, is MIT licensed, and writes every query and decision to an audit trail that generates evidence for HIPAA, GDPR, and PCI DSS. See the source on GitHub.

Frequently asked questions

Which role do I need for the snowflake create user step?

You need an admin role that holds global user creation privileges in the account. Most teams use the dedicated user admin role instead of the top system admin role.

Should a new user get direct table permissions?

No, Snowflake does not grant table permissions straight to user accounts. You always grant table permissions to a role, then assign that role to the user.

How should service accounts log in after creation?

Service accounts should use key-pair secrets or external token workflows instead of plain passwords. You should also assign them a narrow custom role with no human login rights.

The query runs. The emails stay hidden.