Preset Feature Feedback
What is the problem or goal you're trying to solve or accomplish?
Currently, when a user has no matching RLS rule or when the filter value resolves to empty, Preset executes the query without any restriction. This "fail-open" behavior is a security risk in environments where data access must be strictly enforced as a misconfiguration or missing rule silently exposes data instead of blocking access
How are you solving it currently?
Using Base Filters as a workaround, which apply to all users regardless of role. However, this is not a true fail-closed mechanism as it doesn't account for dynamic filter values resolving empty or for cases where no rule matches a specific user.
What is your recommended solution?
Provide a configurable fail-closed mode at the dataset or workspace level that blocks query execution when no RLS rule applies to the requesting user, or when the RLS filter value resolves to null/empty. Access should be denied by default in these cases, with an explicit opt-in to allow unrestricted access.
