Ask the builder to make a table private for each user's own records, or admin-only for records managed by you and your admins.
On a published app, only an empty table can be made more private. A populated table requires a planned copy into a new table. Do not delete records to bypass the refusal.
Choose the access setting
Open Dashboard → Schema to see each table's setting:
| Setting | Who can access it |
|---|---|
| Public | Anyone can read |
| User-scoped | Each signed-in user sees their own rows |
| Team-scoped | You and the app's admins; regular users cannot read or change rows directly |
| Lead capture | Anyone can submit; only admins can read |
| Members only | Users with the required role |
For example, ask: “Make the notes table private, so each user sees only their own notes.”
Change an empty published table
- Ask the builder for the new access setting.
- Check it in Preview.
- Publish before adding private records.
Preview and the live app share records. Keep the table empty until the access change is published.
Change a table in an unpublished app
The builder can tighten access while keeping existing rows and their IDs. It asks for confirmation before tightening public access and saves a restore point.
The switch can remove previous ownership fields. Export the table first if you need that information.
After the switch, existing rows may be hidden because their new team or owner field is empty:
- For admin-only access, ask the builder to fill missing team IDs.
- For private access, explain how to identify each row's owner and ask it to assign them.
- Check the records before changing another table.
If your live table already has records
- Export a backup.
- Ask the builder to create a new, empty table with stricter access.
- Plan a server-side copy that checks the operator's permission and preserves each record's owner.
- Test the copy and access in a separate test app.
- Verify every copied record before emptying the old table.
Support can help plan the copy, but cannot tighten the populated table or move its records for you.
Check custom endpoints
Signed-in endpoints using system access can read all rows. They must authorize the caller before returning records. Admin-only writes must include the app's team ID.
Require sign-in and appropriate permissions for endpoints accessing private data. A browser-supplied user ID is not proof of identity. Keep email addresses and other private fields out of public tables.
Test access with separate accounts
Page visibility and table access are separate. Hiding a page or filtering rows in the browser does not protect a public table.
Test as a signed-out visitor and two separate non-admin users. Confirm that one user cannot read, update or delete the other's records, including through the API. Owner/admin access is not a substitute for this test.
Use synthetic records: Preview and the live app share data. For a separate copy, see Remixing and testing an app. Builder messages use credits.