Sharepoint - What are the best practices for structuring and managing rights for cross-team folders?

For this scenario, the better practice is to organize around permission inheritance and minimize unique permissions on subfolders.

Key guidance:

1. Prefer separate sites or libraries for content with different security needs

• For sensitive or differently shared content, create a site or library specifically for that content rather than scattering unique permissions across many folders.
• This gives better visibility and governance than sharing many subfolders individually.

2. Avoid relying on many shared subfolders and ad hoc links

• Sharing individual folders or files creates additional permission scopes.
• If this is done at large scale, it can become hard to manage and can lead to performance and operational issues as unique ACLs accumulate.
• A shared link is not the best long-term governance model for recurring cross-team collaboration.

3. Use folder-level unique permissions only when the folder truly needs different access

• If the Recruitment folder must be editable by both HR and Management while the parent Personnel Management folder should not be, breaking inheritance on that folder is supported.
• In that case, assign permissions directly to the appropriate users or groups on the folder, rather than broadly sharing the parent.

4. Group content by common access pattern

• If several HR folders are routinely shared with the same other team, placing those folders in a dedicated library can be a good governance choice.
• That preserves visibility over what is cross-team content, even if it changes the original business hierarchy.
• This aligns with the recommendation to segment content by security level.

5. Prefer sharing a folder rather than many individual files inside it

• If a set of files has the same audience, put them in one folder and share that folder.
• This uses fewer permission scopes than sharing files one by one.

6. Be careful with parent-folder sharing

• If a parent folder is shared, that access can expose child content in ways that make restricted subfolders harder to manage.
• For restricted structures, share only the specific folders that should be accessible.

Applied to the example:

• If Recruitment is a stable cross-team working area, a dedicated library for HR content shared with Management is the cleaner design.
• If Recruitment is one of only a few exceptions, a uniquely permissioned folder can work, but it should remain the exception, not the pattern.
• Avoid managing this mainly through links. Manage it through clear library or folder permissions.

A practical rule:

• Same audience as parent: inherit permissions.
• Different audience for a whole category of content: use a separate library or site.
• Different audience for a small exception: use a uniquely permissioned folder.

• Overview: Site governance, permission, and sharing for site owners
• Manage Permission Scopes in SharePoint
• Migrating shared files and folders
• Change the permissions on a subfolder
• External Guest Access to SharePoint Online sub folder with restricted permissions - Microsoft Q&A