A NetDocuments repository vs cabinet comparison comes down to scope. The repository is the organization-wide administrative shell that holds every user, group, and global metadata field a legal department will ever create. The cabinet is the storage environment inside that repository where documents, workspaces, and folders actually live. Every item in NetDocuments has to sit inside a cabinet, and every cabinet has to sit inside a repository. A NetDocuments rollout typically moves through discovery, configuration, testing, and hypercare before go-live, and the repository and cabinet decisions made in the first weeks of that process are the ones a department lives with for years.
What is a NetDocuments repository?
A NetDocuments repository is the enterprise-wide administrative environment that governs users, groups, billing, global metadata, and cabinet creation for an entire organization. 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. The numbers bear this out: an analysis of 12,195 confirmed breaches found credential abuse was the most common way attackers got in, at 22 percent. One repository typically covers an entire corporate legal department, no matter how many offices or business units sit underneath it. A repository does not store a single document itself. It is the governance layer that makes every cabinet inside it possible, and it is created and administered by a small, dedicated group of Repository Administrators.
What is a NetDocuments cabinet?
A NetDocuments cabinet is the document-storage and access environment that sits inside a repository, and it is where users actually spend their day. Cabinets hold workspaces, folders, filters, and documents, and NetDocuments treats a cabinet as comparable to a document library, with the difference that a cabinet is not tied to a single office or geography. A department might run a Client Documents cabinet, a Corporate Records cabinet, and an Administrative cabinet side by side inside one repository, each carrying its own access rules, its own activated metadata fields, and its own administrator.
How does NetDocuments repository vs cabinet administration work?
NetDocuments repository vs cabinet administration splits into two distinct roles, and treating them as the same job is where many legal departments first lose control of their document structure. The Repository Administrator creates users, groups, and cabinets. The Cabinet Administrator manages what happens inside one specific cabinet once it exists, including which of those already-created groups get access to it. Even the largest NetDocuments rollouts, spanning offices across every US state, keep a single repository with one disciplined cabinet layer underneath it, and dozens of separately governed environments are never part of the design. A Repository Administrator decides whether a cabinet should exist at all. A Cabinet Administrator decides how that cabinet behaves once it does.
What does a Repository Administrator control?
A Repository Administrator controls the enterprise-wide functions of a NetDocuments environment, from adding a new hire to authorizing a cabinet for an acquired business unit. This is a small group by design, and the role carries the functions that no cabinet-level administrator can touch:
- Internal and external users. Adding users, managing repository membership, and controlling federated identity.
- User groups. Groups are created once at the repository level and reused across every cabinet that needs them.
- Global Profile Attributes. The master metadata taxonomy, including fields like client, matter, department, and confidentiality level, is built here and activated selectively by each cabinet.
- Billing and cabinet lifecycle. Account administration and the creation, archiving, or retirement of cabinets both sit with the repository.
What does a Cabinet Administrator control?
A Cabinet Administrator controls the day-to-day behavior of one specific cabinet, working inside the boundaries the Repository Administrator already set. Most cabinets carry more than one administrator for continuity.
- Default access levels. NetDocuments offers four default access options for a cabinet, commonly described as View, Edit, Share, and Administer, and the Cabinet Administrator assigns them to groups the repository already built.
- Workspace templates. Default and custom templates, folder structures, and list views are configured at the cabinet level.
- Attribute activation. A cabinet activates only the global attributes relevant to its users, which is what keeps profiling clean and searchable.
- Storage mode and collaboration. Editable or archival status, CollabSpaces, and export controls are all cabinet-level decisions.
How many cabinets should sit inside one repository?
Most corporate legal departments need one to three cabinets inside a single repository, well short of the dozen or more that accumulate once every practice group asks for its own space. A workable starting point looks like this:
- Client or matter documents. The primary working cabinet for active legal work.
- Corporate records or internal documents. Board materials, policies, and internal governance content.
- Administrative or restricted documents. Content that needs tighter access controls than the rest of the department.
A fourth cabinet is worth creating only when a specific governance reason demands it, such as a retention schedule, an external-collaboration requirement, or a data-residency rule that genuinely cannot live inside one of the three above. It should stay the exception, never the default response to a new request. A focused departmental NetDocuments rollout typically runs two to four months, including workspace design and training, and a rushed cabinet decision inside that window produces years of cleanup work later. The same discipline applies to platform migrations broadly: a problem caught during discovery costs a fraction of what the same problem costs after go-live, so the repository vs cabinet conversation belongs at the start of the project. Structuring the matter and contract entities a repository will serve should happen alongside it, since both depend on the same underlying decisions.
How does cabinet design affect search and security?
Cabinet design affects search and security because NetDocuments scopes both to the cabinet a user currently has open, and it does so independently of repository-wide access. A user can hold full repository access and still be locked out of a specific cabinet inside it, and a search run from within one cabinet will only surface results from that cabinet.
- Scoped search and access. Cabinet boundaries determine what is findable as much as what is secured.
- Least privilege by default. Cabinet access should start restrictive and expand only where a role genuinely requires it.
- Workspace-level restrictions. Matter-specific sensitivity belongs at the workspace level. A single sensitive file does not justify an entirely new cabinet.
What storage mode should a cabinet use?
A cabinet should run in editable storage mode for active work, supporting uploading, editing, and versioning as documents move through their lifecycle. Editable mode carries the daily document lifecycle, from drafting through versioning and collaboration. Archival mode exists for a different purpose: inactive, read-only, or permanently retained content the department is confident it will never need to change. That makes archival a governance decision, and it deserves to be treated as one, because an archival cabinet may not convert back to editable status under NetDocuments’ rules.
Confirm the consequences with a NetDocuments administrator before switching a cabinet’s storage mode, and treat the change the same way any other configuration change gets validated in a test environment before it touches production.
What are the most common repository and cabinet design mistakes?
The most common repository and cabinet design mistakes come from treating cabinets like folders when they need to function as governance boundaries. Departments migrating off a legacy platform run into this often, including those coming from iManage, where the repository and cabinet concepts map differently and every migration needs fresh planning built around that difference.
- Too many cabinets. Every additional cabinet fragments search, metadata, and administration a little further.
- A single administrator. Critical roles need at least two people so a departure never stalls access decisions.
- Individual access assigned repeatedly. Group-based access keeps periodic access reviews manageable; individual grants make them slow and error-prone.
- Storage mode changed casually. A switch to archival deserves the same release discipline any other configuration change on a legal platform receives, documented and reviewed before it happens.
- No documented cabinet ownership. An undocumented configuration decision becomes a liability the moment the person who made it leaves, and cabinet ownership is exactly the kind of decision that gets lost first.
Conclusion
Getting the NetDocuments repository vs cabinet structure right at the start is the highest-leverage decision in a legal department’s document management rollout. A single repository with one to three disciplined cabinets underneath it will absorb a decade of business change, reorganizations, and platform upgrades without a rebuild, while a repository accumulating a fresh cabinet for every request will need one within a few years regardless. The repository governs the enterprise. The cabinet governs the work. Keeping that boundary clean from day one is what separates a NetDocuments environment that scales from one that eventually needs a rescue project.
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. The legal technology consulting bench includes business analysts and QA specialists who have built and tested workspace structures, documentation, and training materials across matter management and eBilling rollouts spanning more than 100 jurisdictions, so repository and cabinet decisions get made with the downstream administration burden already in view.
For departments mid-migration or facing a compressed go-live date, Basla’s delivery teams scale to absorb configuration, testing, and documentation workload, staying engaged through hypercare once the cabinet structure goes live.
Frequently asked questions
What is the NetDocuments repository vs cabinet difference in practice?
The NetDocuments repository vs cabinet difference comes down to scope: the repository governs the whole organization, including users, groups, billing, and global metadata, while the cabinet is the storage environment inside that repository where documents, workspaces, and folders actually live.
How many cabinets does a repository need?
Most legal departments need one to three cabinets to start, typically split between client or matter documents, corporate records, and administrative content, with additional cabinets added only for a specific governance reason such as retention, security, or regulatory requirements.
Who should be a Cabinet Administrator versus a Repository Administrator?
A Repository Administrator should be a small group responsible for enterprise-wide functions like users, billing, and cabinet creation, while a Cabinet Administrator manages one specific cabinet’s access, templates, and storage mode, and the two roles should rarely sit with the same person across every cabinet.
Can a cabinet be converted from archival back to editable storage?
Archival mode may not convert back to editable status under NetDocuments’ rules, so an administrator should confirm the consequences with NetDocuments before switching a cabinet into archival mode, and should assume the change is permanent unless NetDocuments confirms otherwise.
Does cabinet structure affect document search?
Yes. NetDocuments scopes search to the cabinet a user has open, so a document stored in one cabinet will not appear in a search run from a different cabinet, even when the searching user has access to both.
How long does a NetDocuments repository and cabinet redesign take?
A focused departmental NetDocuments rollout, including workspace design and training, typically takes two to four months, though the timeline extends once migration from a legacy platform or a large shared-drive estate joins the scope.
*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.*