

- #DEFAULT INHERITANCE WHEN CREATING NEW FOLDERS HOW TO#
- #DEFAULT INHERITANCE WHEN CREATING NEW FOLDERS DOWNLOAD#
If you have a huge library while users only need a few specific folders on the computer, the sync button above will download it all to their desktop and create a two-way connection between the two. This syncs the entire library to their computer. When users sync, they typically sync the entire library by clicking on the Sync button.

In this scenario, you will need to create a separate library for invoices, add metadata to that library and leave all the other documents in the other library within folders.Īnother thing you need to consider is OneDrive Sync which is extremely popular among users.

For example, you have various financial documents in a library (invoices, receipts, bank statements, etc.) but want to apply metadata to invoices only. So if you have a single library with many folders and want to use metadata on a subset of files, this isn’t going to work, my friend. Metadata is created at the library level in SharePoint.
#DEFAULT INHERITANCE WHEN CREATING NEW FOLDERS HOW TO#
If you want to learn how to create unique permissions for a library, check out this post.Īnother big decision that might influence your architecture is the use of metadata. Example: You have a Board of Directors Site with various docs, but a subset of those documents needs to be seen by only the subset of board members or Management only. True, you can set unique permissions at the folder level, but it might be a bit “cleaner” to do so at the library (higher) level. There are situations when you might want to have unique permissions for a subset of documents. By default, all libraries on a site inherit permissions from the site itself. The next factor that might influence the decision is security and permissions. This is not a scientific number, just my commonsense recommendation. I usually recommend not to put more than 20-30K of files and folders into a single library. There are well-known limits within SharePoint on how much a single library can handle before it starts to misbehave. The #1 factor that might steer you in the direction of additional libraries is the number of files and folders you have. Should you be creating folders in the existing (default) library or create new document libraries on your site? The answer depends on many factors, which I outlined below. Now that we covered all the necessary background info, back to the original question. Should I create a folder or a library on a SharePoint site?
