Three different integration paths
Keep browser automation, a Chrome extension and live Office add-ins distinct. They have different host permissions, enrollment and lifecycle requirements. A working browser tool or generated Office file does not prove that an extension or add-in is installed and supported.
Chrome enrollment
The intended company integration needs a known employee identity, a company API connection and explicit site or page permissions. Define what page context is shared, which actions require approval and how access is revoked. An integrated release package has not yet been qualified.
Word, Excel and PowerPoint
For a live Office integration, identify the selected document, workbook or presentation and the permission to read or edit it. Handle document switches, unsaved changes, conflicts and closed hosts deliberately. Live add-ins have not completed release qualification; generated-file workflows are a separate scope.
Keep company policy in the path
An integration must not become a second source of authority. Account state, source access and action permissions need to be re-evaluated at the relevant server boundary. A cached client decision cannot extend a revoked permission.
Describe what enters the record
Agree the selected context, intended action, approval and observed result. Record coverage should identify the enrolled surface and its version. Do not interpret an integration as permission to collect unrelated browser history or every open document.
Prepare the pilot handover
List the host application and version, operating system, enrollment method, permitted sites or files, identity setup, support owner and release artifact. Confirm supported and excluded actions before onboarding employees.