How do I set up true household‑level privacy so each family sees only their own data?

Ask for Help
1

I’m building a behaviour‑first financial app where each household needs its own private space. I don’t want users seeing each other’s data, and I don’t want to rely on per‑screen filters that can be bypassed. I need to understand the correct, secure way to structure my tables and relations so that each household has its own isolated dataset.

What is the recommended Glide architecture for:

  • creating a Household table
  • assigning users to a household
  • ensuring all expenses, categories, and settings belong to that household
  • filtering every screen and relation by Household ID
  • preventing cross‑household visibility

I want to make sure I’m following Glide best practices for multi‑user privacy and row‑level isolation.

2

You need to use Row Owners, and Roles as Row Owners.

  • In your Users table, each user should have a Role. For most users, this most likely should be their HouseHoldID.
  • You need to configure your User Profiles, and ensure your Role column is correctly set.
  • In each table where you need the data protected, you should have two columns with Row Owners applied. One will contain the email address of the user that created the record, and the other will contain the name of the Role group they belong to (ie. the HouseholdID)