# More & granular privacy for user profiles and fields

**URL:** <https://meta.discourse.org/t/more-granular-privacy-for-user-profiles-and-fields/86249>\
**Category:** Feature\
**Created:** [26 april 2018 om 20:43 UTC](https://meta.discourse.org/t/more-granular-privacy-for-user-profiles-and-fields/86249 "2018-04-26T20:43:27Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [26 april 2018 om 21:26 UTC](https://meta.discourse.org/t/more-granular-privacy-for-user-profiles-and-fields/86249/2 "2018-04-26T21:26:44Z")

</div>

I have a client with a similar need ([https://meta.discourse.org/t/hide-bio-location-and-website-unless-member-of-specific-group/86014?u=pfaffman](https://meta.discourse.org/t/hide-bio-location-and-website-unless-member-of-specific-group/86014)). They want to control which users can share profile information.

A work-around for your part of your situation would be to have a public and a private certification level field. Users could include it in the private required field and put it in the public field if they so chose. It wouldn’t be that much more difficult to enter it twice than to have a checkbox that said who could see it. That doesn’t solve the logged-in/trust level part, though.

---

_[View the full topic](https://meta.discourse.org/t/more-granular-privacy-for-user-profiles-and-fields/86249)._
