NetDocuments CollabSpaces are shared areas attached to a workspace where internal users and invited external parties work on the same documents inside the document management system. Outside counsel, auditors, and clients see only the CollabSpace they are added to, and the documents stay under the matter’s own security and retention rules. That replaces a patchwork of email attachments and file-sharing links with one governed route.
What are NetDocuments CollabSpaces?
NetDocuments CollabSpaces are collaboration containers, each associated with a single matter workspace, that give external users access to a defined set of documents without exposing the rest of the cabinet. Exposure is costly, since the 2026 edition of a long-running global study puts the average cost of a data breach at $4.99 million, a record high. Each collaboration site automatically inherits the rules, governance, and retention policies of its matter workspace.
That inheritance is the practical difference from email. Every email attachment is a copy the matter no longer controls, and outside parties are a growing risk: an analysis of 12,195 confirmed breaches found third-party involvement in breaches doubled to 30 percent. A document in a CollabSpace stays one document, with one version history and one access list.
CollabSpaces also fit the way in-house teams already organize work around matters. Matter management gives attorneys documents, correspondence, and deadlines in a single platform, and CollabSpaces extend that single place to the people outside the department.
How are CollabSpaces different from secured links and external user access?
CollabSpaces differ from the other NetDocuments sharing methods because they give external users working access to a controlled set of documents over the life of a matter. NetDocuments recommends CollabSpaces for collaboration with clients and third parties.
- Secured links. A secured link gives one recipient view access to one document, typically with an expiration date. It suits a one-off send, and it offers no editing or ongoing collaboration.
- Direct external access. An external user can be granted cabinet rights to folders or whole workspaces for an extended period, with many of the same features as an internal user. This is the broadest option and the hardest to govern at scale.
- CollabSpaces. External users see only the CollabSpaces they belong to, can review and edit what is shared there, and stay within the workspace’s rules.
What changes when you enable CollabSpaces in a NetDocuments cabinet?
Enabling CollabSpaces in a NetDocuments cabinet makes CollabSpaces the default route for external sharing, and in a CollabSpace-enabled cabinet, external groups can have no more than No Default Access, and workspaces are hidden from external users. That is a deliberate tightening, and it changes what existing users can do.
- External groups. External groups are capped at No Default Access on the cabinet, so they see nothing unless it sits in a CollabSpace they belong to.
- Workspaces. External users lose visibility of workspaces and see only their CollabSpaces.
- Security templates. New security templates containing external access rights cannot be created. Existing templates and internal-only templates are unaffected.
There are three exceptions. Secured links still work, content shared externally before CollabSpaces were enabled keeps its access (though no more external access can be added to it), and profile-based security can still grant external access to workspaces. A separate cabinet setting, Enable External Sharing Outside CollabSpaces, controls whether the older direct-access process remains available at all.
Where do you enable NetDocuments CollabSpaces?
CollabSpaces are enabled at three levels: the repository, the cabinet, and the individual workspace. If the CollabSpaces tab is missing from a workspace, one of those three switches is off.
- Repository. A repository administrator turns the feature on once, which makes it available for cabinets to use but switches nothing on by itself.
- Cabinet. Cabinet administrators then enable it for each cabinet that should use it. Start with one cabinet before extending it.
- Workspace. Any user with VES rights to a workspace can enable the CollabSpaces tab. Disabling the tab later does not delete existing CollabSpaces; they simply stop appearing on the workspace page, though links, search results, and the navigation pane still reach them.
Include the CollabSpaces tab in the workspace template for matter types that routinely involve outside parties, so users do not have to switch it on matter by matter.
Who can create CollabSpaces and external users in NetDocuments?
Creating CollabSpaces and the external users who join them is controlled by a repository-level setting and by rights on each CollabSpace. An internal user can create CollabSpace groups and external users in a cabinet only after the setting is enabled and only if they hold VESA rights on a specific CollabSpace.
If you do not want regular internal users creating external users, do not give them VESA on CollabSpaces, and keep that right with a small group such as legal operations or an extranet team. Requests for new CollabSpaces go to the cabinet’s administrators by default, and administrators can route them to a different address, such as a support desk mailbox, so the people who own the process handle them.
Decide this model before rollout. The alternative, where every lawyer can invite anyone, produces a list of external accounts that nobody can audit a year later.
How does access work inside a NetDocuments CollabSpace?
Access inside a NetDocuments CollabSpace starts from the access list its creator sets, and documents added to the CollabSpace inherit that list. The cabinet’s default access is placed on the list by default, and the creator can remove it when the CollabSpace should be tighter than the cabinet.
Every document and folder added to the CollabSpace takes the CollabSpace’s access list, so adding a file to a shared CollabSpace shares it with everyone on that list. Train users to check which CollabSpace they are filing into. Individual documents and folders can still have users added or removed where needed, for example a draft that only the lead outside counsel should see, and changing an access list requires Administer rights on that item.
For a matter with three outside firms, create one CollabSpace per firm. Each firm then sees its own work and nothing from the others.
How do retention and workspace closing apply to CollabSpaces?
Retention and workspace closing apply to CollabSpaces through their parent workspace, because every CollabSpace belongs to one. The records rules you set for a matter therefore reach the documents shared on it.
When a workspace is closed, the effect applies to every document in every CollabSpace in that workspace, and a retention policy applied to a workspace, or to its closing date, applies to all documents in all of its CollabSpaces.
This is where CollabSpaces beat external file-sharing tools most clearly. A document shared through a third-party service has to be tracked and deleted separately, while a CollabSpace document follows the matter’s schedule. If older content still sits in ShareSpaces, plan its move into CollabSpaces as a small migration.
What controls can administrators apply to external users in CollabSpaces?
Administrators can apply repository and cabinet controls that limit how external users authenticate and what they can do once inside a CollabSpace.
- IP restrictions. If the repository restricts sign-in to approved IP ranges, external users would be blocked, so NetDocuments provides an option to exclude external users from those requirements while they reach only the content explicitly shared with them.
- History access. External access to document and CollabSpace history is controlled at the cabinet level. Most legal departments leave it off, since history can reveal internal reviewers and timelines.
- Email Link. A cabinet setting decides whether external users can use the Email Link option to send a document link to others on its access list.
Record each setting and the reason for it in your security design. When an auditor or client asks how external access is controlled, that record is the answer.
How should you roll out NetDocuments CollabSpaces?
NetDocuments CollabSpaces should be rolled out one cabinet and one use case at a time, with the creation model, templates, and external-user controls settled before the first invitation goes out. A pilot of four to six weeks on a single matter type surfaces most of the practical questions.
- Pilot matters. Choose two or three live matters with active outside counsel, and run outside counsel onboarding as a workstream with its own owner and checklist.
- Security testing. Test with real external accounts that should and should not see each CollabSpace.
- User guidance. Give lawyers a one-page guide on which sharing method to use when, because standard software documentation alone rarely sustains long-term adoption.
Fold the rollout into the wider NetDocuments implementation, where cabinets, profiles, and workspace structure are settled before documents move.
Conclusion
NetDocuments CollabSpaces give a legal department one governed way to work with outside parties: documents stay in the DMS, follow the matter’s retention rules, and are visible only to the external users added to each CollabSpace. Enabling them tightens external access across the cabinet, so the creation model, templates, and administrator settings need deciding first. Pilot on a handful of matters, test with real external accounts, and give lawyers clear guidance on when to use a CollabSpace and when a secured link is enough.
How Basla can help
Basla provides certified delivery team members for NetDocuments implementation, including business analysts who design the CollabSpace creation model and external access policy with your legal and IT stakeholders, and QA analysts who test external accounts against real matters before rollout. Basla’s documentation writers produce the administrator guides and one-page user guidance that keep external collaboration consistent after go-live.
Basla delivers legal technology services through staff augmentation or Basla-managed delivery. On other legal platform programs, Basla has created and executed more than 1,000 test records for a CLM rollout and doubled delivery team capacity to meet compressed implementation timelines.
Frequently asked questions
What are NetDocuments CollabSpaces?
NetDocuments CollabSpaces are collaboration areas attached to a workspace where internal and external users work on shared documents inside NetDocuments. Each one inherits the governance and retention policies of its matter workspace.
Can external users see workspaces in a CollabSpace-enabled cabinet?
External users cannot see workspaces in a CollabSpace-enabled cabinet. They see only the CollabSpaces they have been added to, and external groups are capped at No Default Access on the cabinet.
Are secured links still available when CollabSpaces are enabled?
Secured links remain available in a cabinet with CollabSpaces enabled. They give a recipient view access to a single document and suit one-off sends.
Who can enable CollabSpaces on a NetDocuments workspace?
Any user with VES rights to a workspace can enable its CollabSpaces tab, once CollabSpaces are enabled for the repository and cabinet. Disabling the tab later does not delete existing CollabSpaces.
What rights do internal users need to create external users for a CollabSpace?
Internal users need VESA rights on a specific CollabSpace to create CollabSpace groups and external users, and the repository-level setting must be enabled. Withholding VESA keeps external user creation with a small administrative group.
Does closing a workspace affect its CollabSpaces?
Closing a workspace applies to every document in every CollabSpace in that workspace. Retention policies on the workspace apply to those documents in the same way.
*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.*