I have an object workspace-A created by User-A and he wants to share this workspace with another user-B. This works well, by using standard privacy rules, by just having a list of member users on the workspace object and then setting a rule accordingly.
Although user-B will see the workspace, he cannot see who created the workspace (workspace.creator[User]) since users can only see their own data. There are now 2 solutions
A.) create workspace.owner_email [str] field and make it visible
B.) set privacy rule: User: must be loggedin. View: email, but deactivate “Find in Searches”
Something that I do, which I’m not sure if it’s the perfect solution, but it’s what works for me is I create a separate data type for multi-tentant apps called a “User Profile” or “Alias” that has some specific fields attached to it like:
The User
First Name
Last Name
Email
Organization
The reason I do this is so only the people in the same organization (and has admin or the appropriate permission) can view specific things about the user. The condition I set for this in privacy rules is: This user's profile's organization is Current user's lastLoggedInProfile (the type being the same as User’s Profile).
well you can just have all the user information on the profile object, giving you more flexibility. You might just have to sync the user.email field with the profile.email field. probably a viable option. But not obvious when starting with bubble
well my rationale with that is my app actually has someone fill out an application before being a part of that org and they may prefer a different email to use at that org for communication vs. the email they use to log into their overall account
