# Row-level security denies an empty value

By Steven Van · 2026-09-02

Rules checking signed-in user information previously could match records with missing fields, potentially exposing unintended data.

Missing user information could previously let a row-level security rule in [Base44](<https://creatorstoolbox.com/tools/base44>) match records whose field was also missing, potentially exposing more data than intended.

Following the September 2 update, rules that check a value from the signed-in user deny access if that value is empty or cannot be resolved. Base44 links to its [data management documentation](<https://docs.base44.com/Building-your-app/Managing-your-app-data>) for more information.

[![](<https://docs.base44.com/images/base44-docs-og.png>)](<https://docs.base44.com/Building-your-app/Managing-your-app-data>)

![Base44](<https://www.google.com/s2/favicons?domain=base44.com&sz=128>)

Base44

AI app builder — describe what you want and get a fully functional web app in seconds, no coding required.

[View Base44 →](<https://creatorstoolbox.com/tools/base44>)

[Original source](<https://docs.base44.com/changelog/product#september-2-2026>)

[Read Row-level security denies an empty value on Creators Toolbox](<https://creatorstoolbox.com/blog/base44-row-level-security-denies-an-empty-value>)

---
Canonical source: https://creatorstoolbox.com/blog/base44-row-level-security-denies-an-empty-value