Hide SharePoint Folders in a Flat Library View Without Changing Access

A flat SharePoint library view can show files from folders without making users navigate the folder tree. It changes presentation only. It does not delete folders, move files or prevent someone with permission from opening the folders another way.

That security boundary is the most important part of this guide.

Create the flat view

Use an account allowed to create public views in the library.

1. Open the document library.
2. Open the current view menu and choose Save view as or Create new view, depending on the experience shown in your tenant.
3. Give the view a clear name such as All documents, no folders.
4. Open the library's view settings.
5. If the Folders section is available, select Show all items without folders.
6. Save the view.
7. Test it with an ordinary member account.

Microsoft documents how to create, change or delete a list or library view. Labels and options can differ between modern and classic experiences, so use the current view settings presented by your tenant.

What the view changes

The view can give users one sortable list of files while preserving the existing folder structure underneath. That can help during a gradual move towards metadata because people can filter by columns without first knowing a folder path.

The view does not:

• remove folders from the library;
• change links to documents;
• break or restore permission inheritance;
• prevent sync clients or other views from exposing the folder structure;
• turn folder names into metadata;
• prove that all files are correctly classified.

Do not use a view to hide sensitive content

Views are navigation aids, not access controls. If a person has permission to a folder or file, removing it from one view does not revoke that permission.

For genuine access separation, use SharePoint permissions and preferably keep permission boundaries simple. Microsoft's permission-scope guidance explains that unique permissions create additional scopes and recommends careful management at scale.

A separate site or library is often clearer than hundreds of uniquely secured folders. Before changing access, record the current owners and groups, test inheritance, and have a recovery plan.

Decide whether folders are actually the problem

Folders are not automatically wrong. They can provide a familiar navigation model, support a business boundary or preserve a migration path.

Flattening helps when:

• users need to filter the same files by several attributes;
• deep nesting makes content hard to discover;
• folder names are being used as inconsistent categories;
• a process needs reliable columns rather than path parsing.

Keep folders when the hierarchy is understood, stable and meaningful. Do not replace one clear structure with twenty mandatory metadata fields nobody maintains.

A safer migration from folders to metadata

1. Inventory the folders and identify what each level means.
2. Create only the columns that support real filtering or governance.
3. Populate metadata on a small sample.
4. Create the flat view and test search, filtering and links.
5. Test with owners, members and visitors.
6. Keep the original view available during the pilot.
7. Record how to reverse the change.

If files appear missing, switch back to an unfiltered view and inspect view filters, item limits, content approval and permissions separately. Do not assume the files were deleted.

Evidence boundary

A successful flat view proves that the selected account can see files without folder navigation. It does not prove that every user sees the same set, that permissions are correct or that search has indexed everything.

For practical information-architecture and permissions decisions, join the SharePoint & Teams Admins Space.

Sources

• Microsoft Support: create, change or delete a view
• Microsoft Learn: manage permission scopes in SharePoint
• Microsoft Learn: permission levels and inheritance
• Microsoft Learn: modern list and library customisation