When the Include individual person documents setting is turned on in the Group Type Editor, the Group documents screen displays individual documents for all people within the group and for anyone with a personal relationship to a person in the group. This is working as intended.
This article explains what the setting does, why you may see documents for related people, and what options are available if this does not suit your needs.
What the setting does
The Include individual person documents setting in the Group Type Editor controls whether individual person documents are visible in the Group documents screen.
When this setting is turned on, the Group documents screen includes individual documents relating to anybody within the group or with a personal relationship to the person. This means you may see documents for related people, such as parents, carers, or other individuals linked through personal relationships.
Why you see documents for related people
The 'show more people' functionality is working as intended. The setting is designed to surface all relevant documents connected to the group, including those belonging to individuals who have a personal relationship to the person. This is to provide a broader view of documentation linked to the group.
What are your options
If you do not want workers to see documents for related people in the Group documents screen, you have the following options:
Turn off the setting. If the current behaviour does not suit your needs, do not activate the Include individual person documents setting in the Group Type Editor. Linked documents for individuals and related people can still be accessed via hyperlinks to the relevant person summaries.
Record group work with one subject. Some customers choose to record all workflow where possible for individuals who are in a group as group work, with just one subject. This allows all relevant documentation to be seen in the same place without enabling the broader setting.
Will this change in the future
We recognise that there are alternative ways this could work and the benefits of those alternatives. This is something we have on our backlog for potential future development. However, we are unable to prioritise this at present above other items, and it is not currently on our roadmap for delivery.
📌 Note: This article relates to Salesforce case 500dO00000IcLPGQA3.