After Microsoft 365 repositories are connected, your organization should approve only the SharePoint sites, libraries, or folders that are allowed for matter-linked document storage.
Why the allowlist matters
Divorcepath can sync available Microsoft 365 locations, but synced locations are not automatically open for use. Approval lets your organization decide which repositories should appear to end users.
Step 1: Sync available locations
From your organization’s Microsoft 365 repository settings, sync locations after consent is complete. Divorcepath will pull available SharePoint sites and libraries for the connected tenant.
Step 2: Review the synced results
Check the available locations carefully. Confirm site names, library names, and whether each location belongs in the Divorcepath workflow.
Step 3: Mark approved locations as allowed
Enable only the sites, libraries, or folders your organization wants people to use. Any synced location that is not marked as allowed should remain unavailable to end users.
Step 4: Re-sync when your Microsoft structure changes
If new sites or libraries are created in Microsoft 365, run another sync and review the results again before allowing them for use in Divorcepath.
What success looks like
- users see only approved repository locations
- pilot matters can be linked to the correct library without exposing unrelated repositories
- changes to Microsoft 365 locations can be reviewed through a re-sync process before becoming available
Common issues
- A location is visible in Microsoft but not in Divorcepath: run a sync and confirm the integration is fully connected
- A location appears but cannot be selected: it may not be marked as allowed yet
- An existing matter link stops working: the linked location may no longer be allowed for the organization
Best practice
Keep the allowlist intentionally small during rollout. It is easier to expand from a controlled set of approved libraries than to remove access after users have already started saving documents.
