Keep the file beside the work around it.
When people download an Office file and switch tools, the record, access decision, and next action can become disconnected. An embedded document surface keeps that context together.
Files are often the last step outside the product. Office SDK gives your web product an embedded Office document surface so the file can stay with the work while your system keeps ownership of users, files, permissions, and business data.
A sample Office surface for products that keep a document beside the work around it.
Use these pages to decide which workflow, format, and ownership boundary should be validated first.
When people download an Office file and switch tools, the record, access decision, and next action can become disconnected. An embedded document surface keeps that context together.
Open Word, Excel, and PowerPoint files beside the record, task, or process that gives them meaning. Keep the next action close to the document.
Give teams an editing and review surface without sending them to a separate file product. Confirm the exact file and editing behavior for the target workflow.
Move Office files into the workflow your product provides, then use the documented API and callback path to apply your own storage and versioning rules.
Your backend supplies file, user, permission, and organization context through the documented integration surfaces. Storage, access decisions, and business records remain with your system.
Office SDK is an embedded web document surface for products that need Word, Excel, or PowerPoint work to stay beside the surrounding record, permission, and business workflow.
Word, Excel, and PowerPoint are the first format families to validate.
Preview, collaboration, import/export, content operations, and callbacks have different acceptance criteria.
Your product owns business data and access decisions; the embedded surface handles document work.
| User action | Best fit | Validate before launch |
|---|---|---|
| Inspect a file | Preview | Format coverage, access checks, and first-open latency |
| Change document content | Edit | Save path, version identity, and concurrent work |
| Move a file through a process | Import or export | Conversion fidelity, ownership, and result write-back |
The host product remains the authority for user identity, organization membership, file storage, permission decisions, business records, and the workflow state that surrounds a document. The embedded surface should receive only the context required for the current action. Make that boundary visible in the design review so a successful editor demo does not silently become a new storage or authorization system.
A useful acceptance record names the test file, user role, browser, operation, source version, returned result, and owner of the next step. Repeat the path after an expired access decision and a failed conversion. Keep the evidence with the release or business record that depends on it; a screenshot alone cannot prove that a later version was saved or that a denied request stayed denied.