01 / CONTEXT
Start with the product record.
Identify the user, organization, business record, file identifier, and permission decision that should surround the document surface.
INTEGRATION WORKFLOW
Map the file workflow before you choose the API path.
A useful Office integration has a clear owner at every step: your product provides context and access decisions, Office SDK provides the document surface, and your backend applies the documented result path to the business workflow.
OFFICE SDK / INTEGRATION WORKFLOW
12345
ILLUSTRATIVE SAMPLE / OFFICE WORKFLOW
Keep the file
with the work.
A sample Office surface for products that keep a document beside the work around it.
Illustrative sample
Product context → Office surface → business result
A CLEAR BOUNDARY
Useful detail for the next technical question.
Use these pages to decide which workflow, format, and ownership boundary should be validated first.
Your system keeps file storage and permissions.
Preview, edit, review, import, and export are separate decisions.
Callbacks and SDK surfaces connect the document to your product.
02 / SURFACE
Choose preview, edit, review, or conversion.
Select the Office SDK surface that matches the user action. Do not turn a preview requirement into an editing promise.
03 / CALLBACK
Let your backend supply the boundary.
Use callback and integration parameters to provide file, user, organization, and permission context from the system that owns them.
04 / RESULT
Apply the result to the system of record.
Use the documented result path, then apply your own storage, versioning, business-record, and downstream workflow rules.