Preview and edit files where teams keep them.
Keep document actions close to folders, records, permissions, and sharing rules owned by the content platform. Storage and access rules remain host-owned.
Office SDK is useful wherever a file is part of a larger decision. Use these solution patterns to find a high-intent workflow, then validate the exact format and the boundary your application owns.
Use these pages to decide which workflow, format, and ownership boundary should be validated first.
Keep document actions close to folders, records, permissions, and sharing rules owned by the content platform. Storage and access rules remain host-owned.
Let reviewers see the source document alongside comments, approval state, and the business context that drives the next step. Approval state remains host-owned.
Give learners, researchers, and knowledge workers a familiar Office surface without losing the surrounding product workflow.
Connect proposals, statements, plans, and other Office files to the customer, project, or finance record that gives them meaning.
Office SDK is an embedded document surface for products where an Office file is part of a larger task and the host product must keep the record, permissions, and next decision in one workflow.
Content platforms, review and approval, education and research, and business systems cover the main entry points.
Word, Excel, and PowerPoint files can be evaluated inside the surrounding product context.
The document version and the host business record must point to the same completed action.
| Use case | Document sits beside | First proof point |
|---|---|---|
| Content platform | Folder, owner, sharing rule | Open and edit a representative file under ordinary permissions |
| Review and approval | Comments, decision, submitted version | Trace one approval to the exact document revision |
| CRM or ERP | Customer, project, or finance record | Save the result and reopen it from the business record |
| Education or research | Course, report, or knowledge context | Complete the learner or researcher task without a download detour |
A solution page should lead with the work people are trying to complete, not with a generic editor promise. Identify the customer, project, case, course, or approval record that gives the file meaning. Then decide which document action belongs beside it and which events must remain in the host system for audit, reporting, and recovery. This framing keeps the first proof point measurable for both product and operations teams.
A content platform, review workflow, and finance record can all use an embedded document surface while requiring different permissions, version rules, and handoffs. Treat each as a separate proof point. A successful preview does not prove that approval, export, or downstream reconciliation will work without additional tests and an owner. Keep the acceptance result tied to the exact record and file version that the business process will use.