How to Configure Make ClickHouse Credentials
You set up make clickhouse credentials by creating a database user and saving those details in your automation tool. You should assign a minimal role to that user so the automation workflow only touches required tables. Many teams use a single admin account when they first link their workflows to the database. That broad account lets every scenario read all tables, modify data, or drop key schemas. Scoping the database account before you save the secret stops runaway workflows from hurting produ
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 set up make clickhouse credentials by creating a database user and saving those details in your automation tool. You should assign a minimal role to that user so the automation workflow only touches required tables. Many teams use a single admin account when they first link their workflows to the database. That broad account lets every scenario read all tables, modify data, or drop key schemas. Scoping the database account before you save the secret stops runaway workflows from hurting production data.
How to set up make clickhouse credentials in your database
ClickHouse treats users, roles, row policies, settings profiles, and quotas as access items you manage with SQL. Before you create accounts with SQL, you must turn on SQL-driven access control in the server setup. This step needs a storage folder path on the server and an admin user with management rights. Once that is active, an admin with user creation rights can make a fresh account for your workflows. Remember that a database user can only hand out rights that they already hold themselves.
When you create the account, you define how the user logs in and which hosts can reach the server. You also attach default roles and specific user settings during this step. Instead of giving the workflow account full read rights on a whole table, you can grant read rights on specific columns. If a user only has rights on two columns, queries that ask for a third column will fail. Queries that ask for all columns at once will also fail unless the table only has those two granted columns. Starting in version 24.10, you can also grant rights across tables that share a name prefix using a trailing star. After you build this scoped user and role, you enter the host, user, and secret into your workflow tool.
What native database roles solve and what they leave open
Native roles and column grants do a great job of limiting which tables and columns an automation account can touch. Host limits also help by blocking login attempts from unknown networks. These native controls decide who can log in and which objects their role can see.
Still, static database accounts still leave big gaps in day-to-day operations. Once the workflow logs in, the database cannot tell which team member built or triggered the scenario. Every query from every automation workflow shows up in the database logs under the exact same shared user name. If a permitted column holds sensitive data like emails, phone numbers, card numbers, or national IDs, the database sends the raw values straight to the workflow. Static passwords saved in third-party tools also need manual rotation, which can break active workflows when someone updates a secret. Teams often need a way to inspect individual queries in flight and rewrite sensitive fields in results without changing every scenario.
Best practices for ongoing credential hygiene
Treat every automation scenario according to the exact data it needs to read or write. Group common table and column needs into clear SQL roles rather than granting rights straight to user accounts. If one workflow only reads daily totals and another writes event logs, give each workflow its own database user and role. Set strict quotas on those accounts so a stuck loop in a visual builder cannot eat up all server memory.
Ephemeral Credentials + ClickHouse Access Management: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Review your active accounts and role grants on a regular schedule. Check that column grants do not expose new fields added during recent schema changes. When a workflow retires, drop its dedicated database user right away so old keys cannot be reused.
Add runtime guardrails and masking beside ClickHouse
Database grants and network rules control who can reach ClickHouse. Even so, an allowed client or agent can send an alter mutation that deletes rows or read raw personal data. In practice, hoop.dev runs beside the server as a sidecar for your ClickHouse and checks native TCP queries with no change to your drivers.
With hoop.dev ClickHouse support, guardrails refuse banned queries before they run, and data masking rewrites matched string columns in results. The audit trail logs which entity types were masked and how many without storing raw values. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.
Frequently asked questions
Why did my query for all columns fail when using scoped make clickhouse credentials?
When you grant read rights on specific columns only, ClickHouse blocks queries that ask for all columns at once by default. Your automation step must name the exact allowed columns in its query unless the table contains only those granted columns.
How do I turn on SQL user management in ClickHouse?
You must configure the access control storage folder on the server and enable access management rights for at least one initial user. After you enable those settings, you can create users and roles with standard SQL statements.
Can I grant access to a group of tables without listing each one?
Yes, starting in ClickHouse version 24.10, you can use a trailing asterisk on a table name prefix when you grant rights. This lets your role cover all tables that start with that specific prefix.
Short role checks help teams work fast. Simple rules make each review clear. Good logs keep every team safe. Scoped keys stop bad changes early.
Teams test new role rules in staging first. Clear owner lists speed up each audit. Small role scopes cut down on risk. Regular log checks catch drift right away.
Related guides
In this post