How to Configure Make ClickHouse Permissions
You set up make clickhouse permissions by creating a dedicated database user and role. Then you grant that role only the exact tables and columns the automation needs. Many teams take a shortcut and give their Make scenario a shared admin login. That broad role lets one bad module change or read every table in your cluster. A scoped role stops an automation error from breaking production data. How to set up make clickhouse permissions ClickHouse manages users, roles, row policies, settings pr
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 permissions by creating a dedicated database user and role. Then you grant that role only the exact tables and columns the automation needs. Many teams take a shortcut and give their Make scenario a shared admin login. That broad role lets one bad module change or read every table in your cluster. A scoped role stops an automation error from breaking production data.
How to set up make clickhouse permissions
ClickHouse manages users, roles, row policies, settings profiles, and quotas through SQL access entities. Before you create accounts with SQL, you must turn on SQL-driven access control. This setup needs a storage directory set in the server access control path parameter. You also need at least one user with access management and named collection control enabled. An admin can only grant privileges that they hold themselves.
Once SQL access control is active, you create a user account for your Make scenario. Creating this account requires the create user privilege in the database. During user creation, you set the login method, allowed client hosts, and default roles. You can also attach per-user settings profiles to cap query resource usage. Limiting the allowed hosts ensures the account only logs in from expected network addresses.
Next, you assign read or write grants to the role used by Make. If the workflow only pulls reports, grant select rights on specific columns alone. When you grant select on chosen columns, the user can query only those fields. Queries that ask for other columns will fail right away. A select-all star query is also refused unless the table holds only the granted columns. Starting in version 24.10, a trailing asterisk can grant rights by table name prefix.
Where native database roles fall short for automation
Native roles and column grants decide who can log in and which objects they touch. This setup stops a Make workflow from reading blocked tables or dropping schemas. It gives your team a strong baseline for static automation rules.
ClickHouse Access Management + AI Agent Permissions: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Still, static grants do not check what individual queries do while they run. A Make scenario stores a long-lived password or key to run on a schedule. If someone copies that credential, they get the same database rights until you rotate it. Also, column grants are all-or-nothing for each field. If Make needs a table with emails, phone numbers, or card numbers, grants cannot rewrite those fields in results. Database logs also show every action coming from the single shared Make user account. You cannot tell which specific workflow edit or builder triggered a heavy query.
Why column grants break star queries in Make
Visual workflow builders often test connections or pull records by running broad queries. If your Make module runs a star query on a restricted table, ClickHouse refuses it. The query returns no data at all when ungranted columns exist in that table. Builders must list every allowed column by name inside the Make module config. Planning this column list before you build the scenario saves hours of debugging failed runs.
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
Can a ClickHouse user grant permissions to a Make service account?
Yes, if SQL-driven access control is active and the user has the right privileges. A user can only grant privileges that they hold themselves, plus the create user privilege.
Why does SELECT * fail for my restricted Make database user?
When you grant select on specific columns, ClickHouse blocks star queries on that table. Star queries only work if the table contains nothing but the granted columns.
How can I grant Make access to multiple tables with the same prefix?
Since ClickHouse version 24.10, you can use a trailing asterisk in your grant statement. This lets you grant select rights across all tables that share a name prefix.
Related guides
In this post