After Microsoft 365 repositories are connected, your organization can decide how matter folders are created, how documents are named, and whether updates should create new files or continue versioning in place.
Who this is for
This article is for organization admins responsible for shaping repository behavior before a broader rollout to legal teams, assistants, or operations staff.
Settings you should review
- Repository modes: whether your organization will use SharePoint, OneDrive, or both
- Auto-create client folders: whether Divorcepath should create matter folders automatically
- Default folder template: the base folder structure used for linked matters
- Naming template: how saved documents should be named in Microsoft 365
- Upload behavior: whether later saves should create new files or new versions of an existing repository file
Recommended rollout order
- Choose the repository modes your organization will actually support
- Decide whether matter folders should be created automatically
- Set a folder template and naming template that match internal conventions
- Choose the upload behavior for first save and later revisions
- Test with a pilot matter before rolling the configuration out widely
When to use auto-created folders
Enable automatic folder creation when your organization wants a consistent matter structure and does not want staff building folder trees manually. Keep it off if repository locations are managed more tightly outside Divorcepath.
How to think about naming templates
Use naming rules that make sense to legal staff reviewing documents in Microsoft 365, not just inside Divorcepath. A useful naming template should make the document easy to identify without opening it, especially when multiple drafts or matter documents live in the same library.
How to choose upload behavior
Choose a save pattern that matches your repository policy. Some organizations prefer a new repository file for each exported document. Others want a stable repository file that receives new versions over time after the first save is established.
What success looks like
- linked matters save into the expected repository location
- folder structures match your organization’s matter conventions
- document names are predictable and recognizable in Microsoft 365
- later saves follow the expected new-file or versioning behavior
Common mistakes
- rolling out folder creation without testing the template against real matter names
- using a naming template that does not clearly identify the saved document
- expecting versioning to work before the first save has established a repository file
- approving libraries before deciding which repository mode the organization will support
When to contact support
If your organization cannot get the expected folder structure, file naming, or save/version behavior after testing with an approved library, contact Divorcepath support at [email protected].
