How do I set granular permissions in Bubble based on user status?

[Layla.L]

I’ve been building a client portal in Bubble and hit a wall with the permissions logic. I can get basic roles to work, but I’m struggling to set up granular, conditional access where a user’s visibility into certain data records changes based on a status field in their profile. Has anyone else run into this specific issue with complex user permissions?

[Jerry5]

I ran into this last year. I could lock down pages with simple roles, but as soon as a record had a status like private or pending, the visibility checks got brittle. Bubble's privacy rules feel solid, but the UI can still pull fields you meant to hide if you render the data source directly in a repeating group.

[Addison_G]

I attempted a per record filter in a repeating group that used the current user's status vs the record's status. It started leaking data after a status flip. A quick run showed two incidents in a week, so I dropped that approach and kept to broader roles with a field on the record for a visible to tag.

[Aria.A]

Is your status field really the gating signal, or is it just a proxy for something else like org unit or project scope?

[Logan38]

I did a small test app, toggled statuses, and watched what the app fetched. It helped me notice caching and timing mattered, not just the rules. Still not a clean solution, but it kept me from chasing a perfect rule.