That’s the power of query-level approval in the community version — a new way to balance speed with control. It catches risky or expensive queries before they hit production. It gives teams the ability to review, tweak, and approve queries on the spot, without slowing down the rest of the system.
With query-level approval, every request can be held for inspection based on rules you define — complexity, cost, table access, or even certain patterns. This isn’t about blocking everything. It’s about defining guardrails so that the right queries get through instantly while suspicious ones get sent for review. When you have thousands of queries hitting your system each hour, automation decides most of them. For the rest, a human steps in.
In the community version, setup is straightforward. You can apply approval logic to any incoming query. You can log rejected queries, approve them once or always, and set team-wide policies. There’s no need to refactor code or rebuild your pipelines. The approval process works at the request level and integrates with your workflow.