Thanks Jonathan Chandler. Good questions and I know we have discussed directly but I thought I'd respond here to share the recommendations with the Community. 

Folders can have only one “owner” (that is, a group with “write” access), but multiple groups with read access. However, user groups are cumulative, meaning that a user assigned to Group A and Group B will have write access to folders for which either group is assigned as owner. Given these constraints, here is a practical example based on your described scenario:

[Project] (no owner)
    [Content Set A] (owner = Writers, read access = all)
    [Content Set B] (owner = Writers, read access = none) 
    [Content Set C] (owner = SMEs, read access = all)

In this example, users would see the following behavior:
- Content Set A: only users in “Writers” group can edit, all other users can see and reference (read only)
- Content Set B: only writers can edit, other users cannot even see the folder.
- Content Set C: only users in “SMEs” group can edit, all other users can see and reference.

With regard to User groups, they only apply to folder permissions. Keeping in mind that only one group can be assigned as “owner” for a folder, we recommend creating one user group for each type of content that no one else should be able to edit.

In terms of overarching best practices, we recommend to plan out the usage carefully before implementing. Changing folder permissions after the fact is not a trivial process, so we advise to create the minimum number of groups required and do not create groups that “might be” required in the future. You can always add truly required groups later.

Thanks Jonathan Chandler. Good questions and I know we have discussed directly but I thought I'd respond here to share the recommendations with the Community. 

Folders can have only one “owner” (that is, a group with “write” access), but multiple groups with read access. However, user groups are cumulative, meaning that a user assigned to Group A and Group B will have write access to folders for which either group is assigned as owner. Given these constraints, here is a practical example based on your described scenario:

[Project] (no owner)
    [Content Set A] (owner = Writers, read access = all)
    [Content Set B] (owner = Writers, read access = none) 
    [Content Set C] (owner = SMEs, read access = all)

In this example, users would see the following behavior:
- Content Set A: only users in “Writers” group can edit, all other users can see and reference (read only)
- Content Set B: only writers can edit, other users cannot even see the folder.
- Content Set C: only users in “SMEs” group can edit, all other users can see and reference.

With regard to User groups, they only apply to folder permissions. Keeping in mind that only one group can be assigned as “owner” for a folder, we recommend creating one user group for each type of content that no one else should be able to edit.

In terms of overarching best practices, we recommend to plan out the usage carefully before implementing. Changing folder permissions after the fact is not a trivial process, so we advise to create the minimum number of groups required and do not create groups that “might be” required in the future. You can always add truly required groups later.