Steps
- 1
Sign in with an Owner or Admin account, open Workspace administration and confirm who owns access, storage, review policy and audit follow-up before wider rollout.
- 2
Complete Workspace setup to confirm the business details, storage boundary and concurrent-user allowance. Use the readiness view as the first rollout checklist rather than treating an invite as proof of readiness.
- 3
Choose one storage route for the first workflow. In Microsoft 365, select one approved tenant, site, library and folder, grant only the selected-resource permission needed, then record the grant and run Verify. For a DMS, import metadata and locators only.
- 4
Open Users, roles and invites. Keep an Owner active, assign Admin only to named IT or operations administrators, use Partner / reviewer for high-risk review and export decisions, and give day-to-day users the least powerful role that fits their work.
- 5
Open Identity and provisioning. Map only approved Entra groups to Mike AI roles, keep the default role least-privileged, and use the SCIM bearer credential only from the firm identity platform. Disable a mapping before deleting it so access changes remain auditable.
- 6
Open Legal quality. Confirm the workspace jurisdiction policy, review the controlled evaluation thresholds and record any failed citation, deadline, insufficiency or jurisdiction check before allowing the affected output to leave review.
- 7
Invite a small representative group first. Check pending invitations, resend only when needed, and disable stale access rather than removing the audit record. Concurrent active sessions are managed separately from the number of invitations.
- 8
Return to the Workspace for the first operating check. Use the Priority or role queue for urgent blockers, My work to filter assigned matters, and the Review queue for work awaiting a decision. Keep setup work in Admin separate from the daily matter queue.
- 9
After the first working session, open the Feedback desk and record the role, workspace page, category, safe summary and follow-up request. Feedback must not include client document text, email bodies or attachment content.
- 10
Use the linked support guides for task detail and contact support for a configuration issue that cannot be resolved from the workspace. Include the affected page and a safe description of the symptom, never private document content.
Checks
At least one active Owner and one named administrator can access the relevant workspace controls.
The first storage connection is scoped, verified or imported as metadata-only, and has a named owner and revocation contact.
A representative user group has the intended roles, while concurrent-session capacity remains appropriate for the rollout.
Entra group mappings and SCIM provisioning use the intended tenant, least-privileged roles and protected credentials.
The legal-quality dashboard shows the current policy version and no failed high-risk proposition is treated as export-ready.
A test matter appears in the expected role or review queue with its blocker and next action visible.
A screenshot-safe feedback item can be recorded and the support route is available to administrators.