Hmm, I’m not sure I fully understand the question, and I may not know the answer anyway. When you say privacy settings, do you mean actual privacy rules that are tied to a public/private setting on the User data type?
Let me share the problem I am trying to solve. May be you have a different way to solve this. I want each user to have the ability to turn their profile to public or private. For example, how LinkedIn makes the user link active/inactive based on user’s choice. I know one way to do that would be to create/update separate data types.
However, a smarter way would be to create two user profiles with different privacy settings. Logically, the one with public access should be part of dynamic site map. I am just trying to confirm if you or anyone else has has tried it.
We automatically filter URL’s for you based on Privacy Roles. If you want to make sure an individual URL doesn’t show up, make sure that a non-logged-in user (e.g. Google’s crawler) doesn’t have “Find in Searches” permissions.
Just create the privacy setting around the yes/no field on the user.
Conventionally, you build redirection to an app where user roles (“private user” vs “public user”) are allowed or not to pages. Place a condition on every page (example inside a reusable header) where you allow user roles or not to pages (there are creative ways to use the index page and option sets with settings for pages and user roles).