Can each user see only their own records?

Yes, without code. Connect the records to the Users table and add a row-level security policy so each user gets only the records connected to them.

  • Verified Nov 22, 2026
  • Classic builder
  • Tadabase AI
  • Available on: Business Starter, Business Growth, Business Pro, Business Elite

On this page
  1. Set it up
  2. What catches people out

Yes, without code. Connect the records to your Users table (for example an Assigned to connection field on a Jobs table), then turn on row-level security on that table's Security tab and add a policy that gives users only the records connected to them. Tadabase applies the policy on the server each time the table is read or changed, so a page, form or API call cannot hand someone another user's records.

Set it up #

  1. Connect the records to users On the table you want to protect, add a connection field to the Users table and fill it in with the user each record belongs to.
  2. Turn on row-level security In the Data Builder, open the table, click the Security tab and turn on Enable row level security. Under Where these rules apply, choose Everywhere (or Classic app & REST): the default, API, Vibe & AI, does not filter classic app pages. Add admins under Bypass Roles if they should see everything, then click Save Settings.
  3. Add a policy Click Add Policy. Choose who it is for (Specific Roles or Any Logged in Users), the operations (Read, plus Update if they edit their records), and under Which records can they access? pick the Connected using "<field>" field shortcut. Give it a Policy Name and click Create Policy.
  4. Check it Open Row Level Security Overview from the Data Builder menu, click View Permissions As and pick a test user to see exactly which records they get.

What catches people out #

  • Once row-level security is on, a user that no active policy matches gets no records from that table. Add a policy (or a bypass role) for every group that needs access.
  • Only the matching policies with the highest Priority count, and policies tied at that priority add together. A broad policy that gives Any Logged in Users all records, at the same or a higher priority, opens every record to everyone: disable it, or give your narrower policy a higher priority.
  • Access follows the connection field: remove a user from the field and that record is no longer theirs.
  • Hiding a component, a column or a form field only changes what that page shows. For anything that must stay private, use row-level security, and page security for who can open a page.
  • Row-level security does not filter the builder, workflows, or REST API calls made with only the app's API key and secret.
  • The Signup component has no setting that picks a role, so don't add the Role field to a sign-up form: anyone signing up could choose a role with more access.

Full steps, field-level hiding and the policy options: Limit which records each user can see and Control which records each user can see.

Was this page helpful?

Something wrong or missing on this page? Tell us.