it depends on what you mean by “planned” - it’s definitely a much needed feature and it’s on the roadmap, but what’s missing at the moment is a good idea how to realize this a) technically in the backend (object attributes? Access control lists? Filters?) and b) from a user facing perspective (frontend).
For instance, Gramps has 10 different primary object types and “Person” is just one of them. The degree of relationship is highly problematic as being what determines access because it is 1) slow to compute, so would have to be continually recomputed and cached and 2) it does not uniquely determine the access rights for other object types like media objects, sources, citations, places, events etc. One could argue that objects linked to a person I cannot view should not be visible, but what is the exact criterion? What about places linked to an event I cannot view? What about notes linked to sources linked to people I can view as well as people I cannot view?
If somebody has ideas how to solve this in a clean and, most importantly, intuitive manner, please let me know.
Here is the feature request (please comment if you have concrete suggestions, not for +1):
And by the way this has been discussed several times before: