Linking a matter to a repository tells Divorcepath where documents for that client file should be saved in Microsoft 365.
Before you link a matter
- Microsoft 365 repository access must already be connected
- the repository location must be approved for organizational use
- the matter should already exist in Divorcepath with the correct client information
Step 1: Choose the provider and approved location
From the matter or client file, select the Microsoft 365 repository option and choose one of the approved repository locations made available by your organization.
Step 2: Save the matter link
Once linked, the matter stores the external container information needed for later document saves. This is the connection Divorcepath uses to write documents into the right Microsoft 365 destination.
Step 3: Save the first document
The first repository save creates the external file reference in Microsoft 365. After that initial save, later updates can follow your organization’s configured upload and versioning behavior.
Step 4: Create later versions
If the document has already been saved to Microsoft 365 once, future saves can create a new repository version instead of creating a separate new file. This depends on the document already having a valid external file reference.
What success looks like
- a matter is linked to an approved Microsoft 365 location
- the first save writes the document successfully into that location
- later saves update the same external file through the configured versioning path
Common issues
- The matter cannot be linked: the repository location is not allowed for the organization
- The first save fails: repository access may not be fully connected, or the linked location may not include the necessary Microsoft drive information
- Versioning fails: the document has not been saved to Microsoft 365 yet, so there is no existing external file to version
- The link stops working later: the approved location may have been removed from the organization’s allowlist
Best practice
Test one real matter end-to-end: link the file, save the first document, then save a new version. That confirms the full repository workflow is working before you train a wider group.
