SOLVED

Breaking Inheritance on a Document Library in an Office 365 Group Site

%3CLINGO-SUB%20id%3D%22lingo-sub-50024%22%20slang%3D%22en-US%22%3EBreaking%20Inheritance%20on%20a%20Document%20Library%20in%20an%20Office%20365%20Group%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-50024%22%20slang%3D%22en-US%22%3E%3CP%3EInteresting%20situation.%20I%20have%20a%20requirement%20to%20add%20an%20additional%20library%20to%20the%20Site%20of%20an%20Office%20365%20Group%26nbsp%3Band%20break%20the%20inheritance%20and%20remove%20groups%20etc.%20It%20seems%20that%20when%20you%20try%20to%20break%20inheritance%26nbsp%3Bin%20an%20Office%20365%20Group%20Site%20the%20options%20are%20not%20available%20(greyed%20out)%3F%20I%20can%20break%20inheritance%20OK%20but%20cannot%20remove%20groups.%20Can%20add%20them%20OK%20but%20not%20remove.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20else%20experience%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-50024%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%20Groups%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-58243%22%20slang%3D%22en-US%22%3ERe%3A%20Breaking%20Inheritance%20on%20a%20Document%20Library%20in%20an%20Office%20365%20Group%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-58243%22%20slang%3D%22en-US%22%3E%3CP%3EUpdate%3A%20%26nbsp%3BI%20stand%20corrected%2C%20you%20can%20actually%20break%20the%20permission%20of%20a%20document%20library%20and%20give%20access%20to%20certain%20people.%20%26nbsp%3BPeople%20with%20unique%20permission%20won't%20show%20up%20under%20group%20membership%20on%20the%20top%20as%20member%20%2F%20visitor%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F12589i07F061E324753AC9%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Untitled.png%22%20title%3D%22Untitled.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-58204%22%20slang%3D%22en-US%22%3ERe%3A%20Breaking%20Inheritance%20on%20a%20Document%20Library%20in%20an%20Office%20365%20Group%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-58204%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%2C%20Juan.%3C%2FP%3E%3CP%3EI%20must%20admit%20that%20I%20am%20a%20little%20bewildered%20by%20this%20%22instability%22...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-58195%22%20slang%3D%22en-US%22%3ERe%3A%20Breaking%20Inheritance%20on%20a%20Document%20Library%20in%20an%20Office%20365%20Group%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-58195%22%20slang%3D%22en-US%22%3EYes!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-58184%22%20slang%3D%22en-US%22%3ERe%3A%20Breaking%20Inheritance%20on%20a%20Document%20Library%20in%20an%20Office%20365%20Group%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-58184%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20looks%20like%20you%20can%20again%20edit%2Fremove%20default%20permissions%20after%20breaking%20inheritance.%3C%2FP%3E%3CP%3EIn%20fact%2C%20after%20breaking%20inheritance%2C%20I%20have%20successfully%20removed%20the%20Members%20group%20and%20changed%20the%20permissions%20of%20the%20Visitor%20group%20in%20the%20main%20doclib%20of%20a%20private%20Group.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F60%22%20target%3D%22_blank%22%3E%40Juan%20Carlos%20Gonz%C3%A1lez%20Mart%C3%ADn%3C%2FA%3E%26nbsp%3Bcan%20you%20confirm%20it%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-58177%22%20slang%3D%22en-US%22%3ERe%3A%20Breaking%20Inheritance%20on%20a%20Document%20Library%20in%20an%20Office%20365%20Group%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-58177%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20where%20understanding%20the%20requirement%20before%20the%20site%2Fgroup%20is%20created%20will%20be%20critical.%20I%20suppose%20this%20might%20be%20because%20of%20other%20Apps%20(such%20as%20Planner%2C%20Team%2C%20Outlook%2C%20etc.)%20involved.%20%26nbsp%3BI%20think%20the%20approach%20Microsoft%20has%20taken%20is%2C%20member%20of%20a%20group%20is%20a%20full%20member%20and%20you%20give%20have%20restricited%20access%2C%20it%20is%20full%20or%20nothing.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-50096%22%20slang%3D%22en-US%22%3ERe%3A%20Breaking%20Inheritance%20on%20a%20Document%20Library%20in%20an%20Office%20365%20Group%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-50096%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20as%20Juan%20said%2C%20at%20this%20stage%20this%20behavior%20is%20%22by%20design%22.%3C%2FP%3E%3CP%3EIt%20appears%20that%20Microsoft%20consider%20not%20logically%20coherent%20to%20have%20SPO%20resources%20in%20a%20Group%20that%20are%20not%20accessible%20to%20Group%20members.%3C%2FP%3E%3CP%3EHence%20you%20should%20use%20a%20different%20Group%20or%20go%20with%20a%20classic%20team%20site.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-50077%22%20slang%3D%22en-US%22%3ERe%3A%20Breaking%20Inheritance%20on%20a%20Document%20Library%20in%20an%20Office%20365%20Group%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-50077%22%20slang%3D%22en-US%22%3EWe%20have%20been%20discussing%20this%20in%20many%20threads%20in%20the%20Groups%20space...Microsoft%20is%20%22simpliflying%22%20and%20%22changing%22%20how%20security%20is%20managed%20in%20Group%20sites%20compared%20with%20what%20we%20are%20used%20to%20do%20in%20classic%20sites...basically%20what%20you%20are%20trying%20to%20do%20seems%20to%20be%20an%20scenario%20that%20at%20this%20stage%20is%20not%20fitting%20very%20well%20with%20the%20security%20model%20they%20have%20designed%20for%20Groups%3C%2FLINGO-BODY%3E
Deleted
Not applicable

Interesting situation. I have a requirement to add an additional library to the Site of an Office 365 Group and break the inheritance and remove groups etc. It seems that when you try to break inheritance in an Office 365 Group Site the options are not available (greyed out)? I can break inheritance OK but cannot remove groups. Can add them OK but not remove.

 

Anyone else experience this?

7 Replies
best response confirmed by Christophe Fiessinger (Microsoft)
Solution
We have been discussing this in many threads in the Groups space...Microsoft is "simpliflying" and "changing" how security is managed in Group sites compared with what we are used to do in classic sites...basically what you are trying to do seems to be an scenario that at this stage is not fitting very well with the security model they have designed for Groups

Yes, as Juan said, at this stage this behavior is "by design".

It appears that Microsoft consider not logically coherent to have SPO resources in a Group that are not accessible to Group members.

Hence you should use a different Group or go with a classic team site.

This is where understanding the requirement before the site/group is created will be critical. I suppose this might be because of other Apps (such as Planner, Team, Outlook, etc.) involved.  I think the approach Microsoft has taken is, member of a group is a full member and you give have restricited access, it is full or nothing.

It looks like you can again edit/remove default permissions after breaking inheritance.

In fact, after breaking inheritance, I have successfully removed the Members group and changed the permissions of the Visitor group in the main doclib of a private Group.

@Juan Carlos González Martín can you confirm it?

Thanks, Juan.

I must admit that I am a little bewildered by this "instability"...

Update:  I stand corrected, you can actually break the permission of a document library and give access to certain people.  People with unique permission won't show up under group membership on the top as member / visitor 

 

Untitled.png