Forum Discussion
Deleted
Sep 12, 2017Edit vs Contribute when sharing
We've been testing out all the sharing possibilities and having taken the recommendation to drop the default members group permission level to 'contribute', we've noticed that when you share a file with someone (visitor - read only) and "Allow Editing" on the share dialog, a unique permission is created on that file granting the visitor contribute permission.
However, if we leave our members at 'edit' permission level and they do the same sharing with the visitor, no unique permissions are created.
Could anyone explain what might be going on in this situation?
thanks,
Baronne
- Deleted
...furthermore, it seems to me that "Shared with Specific People" doesn't differ much (if at all) from "People with Existing Access" - we still have to remember to check/uncheck the "Allow Editing" first. Here's a series of screenshots in the order of flow for sharing:
- Deletedthe thing is here, it actually makes no sense - to my mind, "People with existing access" is the equivalent of sending someone a link irrespective of their permission and for the system to not break inheritance and create a unique set of permissions on the item/file. But what seems to be happening is that it does in face break the inheritance ... not the expected behaviour!!
- DeletedCan someone test this out for me on their tenant and see if you get this sort of behaviour - I'm currently on a call to Microsoft and I think they're starting to see that this indeed does seem like odd behaviour