How can I segment user data in Bubble so clients only see their documents?

[StellaRM]

I’ve been building a client portal in Bubble and hit a wall with the permissions logic. I can’t figure out how to properly segment user data so clients only see their own documents without writing custom backend code. Has anyone else run into this with complex user roles?

[Mark_J]

Yeah I’ve been there. In my client portal I wanted every document tied to a client and no cross access, and Bubble privacy rules feel like a maze when you don’t want to write backend stuff. We added a Client field on the Document and tried to gate views with Current User's Client, but edge cases kept creeping in and I wasn’t confident every route was solid. It took ages to test.

[RonaldBH]

I remember a sprint where we spent more time chasing visibility bugs than shipping features. The permissions stack felt brittle as we added new roles, and I kept skimming the same data in slightly different screens hoping for consistency. We ended up duplicating a few flows just to keep leaks away, which felt wasteful but it cut the obvious risks.

[Evelyn_S]

Sometimes I wonder if the real snag isn’t the data rules but the navigation. A user lands on a page and the page renders a list that pulls in items you shouldn’t see. It’s not that the backend code is missing, it’s that the front end doesn’t redraw the access guard reliably across all states.

[MiaUD]

One question I keep bumping into in my head is whether the core issue is really how roles are defined or if the data model itself is tangled. If you’re comfortable sharing, what symptom would tell you you’ve hit the real limit here—docs showing up for the wrong client, or something subtler?