Forum Discussion
Solved
SharePoint Online - document and folder permissions inheritance
Hi, I am wondering if there is an easy way to manipulate permissions in SharePoint Online. First I'm going to lay out my assumptions (so they can be challenged) and then some questions. ...
- I was able to fix the problem by re-creating the table. I found that the issue was with the formulas I was using to calculate dates (when I would copy and paste the content as plain text the VSTACK worked). So I recreated the table and reapplied the formulas for dates and it worked.
I do not know why the formulas in the first table were not working originally as they are the same ones used in the current table that is working.
First bullet is correct. Second bullet is not. The way the second bullet works in SharePoint is, as you said, like "how things worked in the 'old world' of file servers where moving the document from one folder to another meant that the file then had the 'protection' of the folder's permissions". That's also how it works in every version of SharePoint assuming the file does not have its own permissions.
That said, you can give a file its own permissions by breaking inheritance with the folder or library that it lives in, but this requires action. So if you don't take that action, the file inherits the permissions of its folder/library. Once you break inheritance, it has its own permissions and retains them no matter where you move the file.
Anyway, I put together a practical guide on permissions, mainly aimed at Site Owners. Check it out here: http://icansharepoint.com/practical-guide-to-sharepoint-site-permissions/
P.S. When you move a file from one folder to another you LOSE the version history of that file, so beware. Version history is one of the most powerful features of SharePoint and the only way to retain the version history if you need to move the file is to migrate the file using a third-party tool. (At least, that's the only way I know of.)
That said, you can give a file its own permissions by breaking inheritance with the folder or library that it lives in, but this requires action. So if you don't take that action, the file inherits the permissions of its folder/library. Once you break inheritance, it has its own permissions and retains them no matter where you move the file.
Anyway, I put together a practical guide on permissions, mainly aimed at Site Owners. Check it out here: http://icansharepoint.com/practical-guide-to-sharepoint-site-permissions/
P.S. When you move a file from one folder to another you LOSE the version history of that file, so beware. Version history is one of the most powerful features of SharePoint and the only way to retain the version history if you need to move the file is to migrate the file using a third-party tool. (At least, that's the only way I know of.)
Regarding the version history it is kept if you move. If you copy instead you keep only the latest version. At least in my experience that's the way it works. I have achieve so either programmatically through the file.move() method or doing drag n' drop using the open in windows explorer feature.
- This is correct. My post dates back to before "Move" was an option in the modern ribbon. I was using the word "move" in the vernacular sense, not the defined action in SharePoint/OneDrive sense.
- Not a problem, I only left the comment for upcoming readers. No criticism intended :)
