Use this checklist to prepare identity, document repositories, permissions, and rollout ownership before you launch Divorcepath Enterprise in your organization.
Who should own setup
Enterprise setup usually works best when it is shared across three roles:
- an organization administrator in Divorcepath
- an IT or Microsoft 365 administrator who can approve consent requests
- a workflow owner who understands how your team manages matters, documents, and approvals
Before you start
- confirm who will complete Microsoft Entra admin consent
- decide whether sign-in should be limited to specific email domains
- decide whether users should receive a default role or be mapped from Entra groups
- decide whether single sign-on should be enforced for your organization
- identify which SharePoint or OneDrive locations should be allowed for document storage
- choose a pilot group of users and a small set of active matters for testing
Recommended setup order
- Set up Microsoft Entra sign-in. Start with identity so you know users can authenticate the right way before you connect downstream systems.
- Confirm roles and access rules. Review default roles, group-based mappings, and whether sign-in should be restricted to your approved domains.
- Enable document repositories. Connect Microsoft 365, sync locations, and allow only the libraries your organization wants to use.
- Test a pilot workflow. Confirm that a pilot user can sign in, open a matter, link a repository, and save documents successfully.
- Plan the broader rollout. Decide who will be onboarded first, how training will be delivered, and who handles support questions during launch.
What success looks like
- approved users can sign in using your organization’s Microsoft identity
- users land with the right role and organization access
- only approved repository locations are available for document linking and saves
- matters can be linked to repository locations and documents can be saved or versioned successfully
- your pilot team can complete a real matter workflow before you expand access further
Common issues to catch early
- admin consent is started by one tenant but completed in another
- allowed email domains are too narrow or missing expected domains
- role mapping is required but no mapping exists for a pilot user
- repository libraries are synced but not marked as allowed
- document naming or folder templates are not set before users begin saving files
When to contact support
If you want help planning the sequence, validating your Microsoft setup, or pressure-testing a pilot rollout, contact Divorcepath support at [email protected] before you expand access to the full organization.
