Data Access Enforcement: Set data permissions once and enforce access on every query

Retool has introduced Data Access Enforcement, a public beta feature for Enterprise Postgres resources that centralizes table-, column-, and row-level access policies at the resource level rather than requiring teams to implement permissions separately in apps, workflows, query libraries, and AI agents. Enabled policies apply consistently across all uses of a resource and are closed by default, meaning access is blocked—including for administrators—unless an active policy grants it. Retool evaluates each query using the signed-in user’s identity, validates tables, columns, and row filters in the backend before execution, and blocks queries it cannot parse or attribute, preventing unauthorized data from reaching the frontend. Policies can provide read-only or write access, restrict columns, filter rows using user attributes such as team or region, and prevent unapproved fields from being accessed by AI agents or other platform components. Organizations are advised to plan policies before activation because unenforced queries will be blocked, connect directly to Postgres rather than through certain pooling proxies, and note that public, embedded, scheduled, webhook-triggered, and otherwise unattributed queries cannot use enforced resources.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.