NetDocuments folders filters saved searches solve the same problem, organizing documents inside a workspace, using three different mechanisms. A folder is a filing location a user files a document into directly. A filter is a metadata-driven view that shows any document matching a profile value, without anyone filing it there by hand. A saved search is a stored query that pulls together documents no single profile value would capture alone. Picking the wrong one turns a workspace into either a folder tree nobody maintains or a filter list nobody understands.
What is the difference between a folder, a filter, and a saved search?
The core difference comes down to how a document ends up inside each container. For context, the 2026 edition of a long-running global study puts the average cost of a data breach at $4.99 million, a record high. A document is filed into a folder directly. A document appears in a filter because it matches that filter’s profile criterion, most commonly Document Type. A document shows up in a saved search because it matches a stored query, which can combine dates, file extensions, profile completeness, or several other criteria at once.
- Folders are static. A document stays where it was filed until a user or an administrator moves it.
- Filters are dynamic. NetDocuments recalculates the filter’s contents every time the workspace is opened.
- Saved searches are dynamic and flexible. They can express a question no single profile attribute answers by itself.
What is a NetDocuments folder, and when should you use one?
A NetDocuments folder is a filing location that a user places a document into intentionally, and it stays static until someone deliberately moves it. Folders earn their place when a workflow genuinely requires a fixed process stage, a specific access-control boundary, or a small, stable structure that will not sprawl as the workspace grows.
- Use a folder for intentional process stages. Intake, drafting, review, and executed are the kind of sequence a folder represents well.
- Use a folder when access control depends on the stage. A folder-level security setting can change what happens to a document’s access rights once it is filed there.
- Avoid using a folder to reproduce metadata. If Document Type already captures the same distinction a folder would represent, the folder duplicates work the profile attribute already does.
How do NetDocuments folders filters saved searches work together inside a workspace?
NetDocuments folders filters saved searches work together inside a workspace by covering three different organizational needs at once: intentional filing, automatic classification, and flexible monitoring. A well-designed matter workspace typically uses a small set of folders for genuine process stages, a handful of filters tied to Document Type, and a few saved searches for the questions that change over time, such as documents added recently or contracts renewing within 90 days.
- Folders represent process. Where a document sits in a defined workflow.
- Filters represent classification. What kind of document it is, based on metadata already captured.
- Saved searches represent monitoring. What a user needs to keep an eye on, independent of where anything is filed.
How do filters organize documents automatically by Document Type?
Filters organize documents automatically by reading a document’s profile value the moment the workspace opens, so a document profiled as a Contract appears in the Contracts filter without anyone dragging it there. NetDocuments can auto-create these filters from a Workspace Template, generating an organizing filter for each value in the attribute the template is built on.
- Filters follow the profile. A reprofiled document moves between filters automatically, with no manual refiling required.
- Filters can be predefined or auto-created. An administrator can configure specific filters in advance, or let the template generate them as new profile values appear.
- Filters stay accurate only if the metadata does. A document profiling design that keeps Document Type clean and controlled is what makes filter-based organization reliable. Research put poor software quality’s US cost at $2.41 trillion in 2022, and a drifting filter view adds to it.
What happens when a document is filed before its filter exists?
A document filed into a folder and then profiled can end up without a matching filter if that filter did not already exist in the workspace at the time. This is a real gap between filing behavior and filter creation, so an administrator has to decide deliberately whether a workspace relies on auto-created filters, predefined filters, or a combination with clear responsibility assigned.
Predefine filters for known values: a workspace built around a stable set of Document Types can have its filters set up in advance, closing the gap entirely. Then monitor for orphaned documents with a saved search that catches profiled documents with no matching filter view, the edge case predefining cannot fully prevent.
What are Saved Searches best used for?
Saved Searches are best used for questions that no single profile value answers on its own, such as incomplete profiles, documents added in the last ten days, files with a specific extension, or contracts expiring within a defined window. A saved search stores that combination of criteria once, so anyone with access returns to the same live query without rebuilding it each time.
- Incomplete or unprofiled documents. A recurring saved search here doubles as the cleanup queue for profiling quality.
- Recent activity. Documents added or modified within a defined window, useful for a status check without opening every folder.
- Renewal and expiration windows. Contracts or obligations coming due within 90 days, built directly from date metadata.
Restrict a saved search to its own workspace where that matters, and confirm whether external members should see it at all before turning it on broadly.
What is a Folder Pack, and when does it earn its place?
A Folder Pack is a predefined folder structure that gets applied to a workspace template or added to an existing workspace, giving every workspace built from that template the same starting subfolder layout. A Folder Pack earns its place only when the workflow genuinely needs a repeatable directory structure, such as a fixed sequence from intake through closing.
Use a Folder Pack for a real repeatable process, such as a five-stage litigation or transaction sequence. Avoid one that duplicates metadata: if Client, Matter, Department, or Document Type already captures the distinction, a matching folder structure adds maintenance with no real benefit, the same clutter that shows up whenever a taxonomy is left to grow without a governance owner.
How does refreshing a workspace affect these containers?
Refreshing a workspace can remove and recreate filters and web pages based on the current workspace template, and it can restore Folder Pack folder access back to the template’s original state. A workspace refresh touches both organization and security at once, so it is never purely cosmetic.
Test template changes in a non-production workspace first. The same validation discipline any platform configuration change needs before reaching production applies directly to a workspace template refresh. Check folder security afterward, because a folder’s access rights can reset to the template default, which may not match what a specific workspace needs.
What are the most common mistakes when choosing folders, filters, and saved searches?
The most common mistakes come from treating all three containers as interchangeable filing tools when each solves a genuinely different problem.
- Building deep folder trees that duplicate metadata. A folder structure that mirrors Client, Matter, and Document Type recreates work the profile attributes already do.
- Creating a filter or folder for every possible value. A workspace with dozens of containers becomes as hard to navigate as the folder sprawl it was meant to replace.
- Leaving container decisions undocumented. An undocumented configuration decision becomes a liability once the person who made it moves on, and a workspace’s mix of folders, filters, and saved searches is exactly the kind of decision new administrators have to reverse-engineer later.
- Skipping the security check after a workspace refresh. Assuming folder access survived a template refresh unchanged is a risky assumption to leave untested.
Conclusion
NetDocuments folders filters saved searches each answer a different question about how a document should be organized. Folders answer where something was intentionally filed. Filters answer what a document is, based on metadata that already exists. Saved searches answer what a user needs to monitor right now, independent of filing or classification. A workspace that uses a small, deliberate set of each outperforms one built entirely from a single container type.
How Basla can help
Basla provides certified delivery team members for NetDocuments implementation, covering testing, documentation, and hypercare through staff augmentation or Basla-managed delivery. That includes workspace design worked through business analysts who decide which containers a template should use, and QA specialists who test filter, folder, and saved-search behavior before go-live, drawing on legal technology consulting and delivery experience across matter management and eBilling rollouts spanning more than 100 jurisdictions.
For workspaces already carrying an overgrown folder tree or a confusing list of filters, Basla’s delivery teams can run the audit and consolidation workstream needed to bring the structure back to something users can navigate. A focused departmental rollout typically runs two to four months, including workspace design and training, and these container decisions are usually the ones a workspace lives with the longest.
Frequently asked questions
What is the difference between NetDocuments folders filters saved searches?
NetDocuments folders filters saved searches differ in how a document ends up inside each one: a folder is a filing location a user places a document into directly, a filter is a dynamic view that shows any document matching a profile value, and a saved search is a stored query that can combine several criteria at once, such as a date range with a file extension.
Do documents actually live inside a filter?
No. A document remains filed in its actual folder or workspace location; it simply appears in a filter view when its profile value matches that filter’s criterion.
When does a Saved Search fit better than a filter?
When the view depends on more than one criterion at once, such as a date range combined with a file extension or profile completeness, since a filter typically organizes by a single profile attribute while a saved search can combine several.
What happens if a document is profiled before its filter exists?
The document may not automatically appear in an organizing filter if that filter was not already present in the workspace, which is why administrators should predefine filters for known values or monitor for orphaned documents with a saved search.
When does a Folder Pack make sense?
A Folder Pack makes sense for a genuinely repeatable process, such as a fixed sequence from intake through closing, and should be avoided when the same distinction is already captured by Client, Matter, Department, or Document Type metadata.
Does refreshing a workspace affect folder security?
Yes. A workspace refresh can restore Folder Pack folder access back to the template’s original state and recreate filters based on the current template, so folder security should be checked after every refresh. Assuming it stayed unchanged is not a safe default.
*This article is provided for general information only and does not constitute legal advice. Basla Solutions provides legal technology implementation and support services and does not practice law.*