Office app enablement and installation overview

Office app enablement controls which first-party entry points appear for one owner account. The installable kinds are doc, workbook, slide, mindmap, form, notebook, calendar, tasks, imageProject, workflow, cron, trigger, webhook, and outbound. A new or unset account uses the minimal default, which exposes Notebook only. Enabled apps appear in their Office group and launcher; enabling an app does not create a document, event, board, workflow, or any other resource.

Use arinova.office_apps.enable when the Agent owner asks conversationally to add one or more of those official apps. The action is owner-triggered, additive, idempotent, and unavailable on public surfaces. It accepts at least one unique app kind, preserves every app already enabled, returns newly enabled and alreadyEnabled values, and broadcasts an enablement invalidation so signed-in clients can refresh without a page reload. Dry run reports wouldEnable and does not mutate settings.

This action has ConfirmationPolicy None and DriftPolicy None because it only reveals existing product entry points. It never removes apps, deletes or migrates user data, pauses automations, grants resource access, installs third-party code, or performs the app’s underlying work. App removal is a separate user-interface operation; removing an entry point retains the owner’s data, and active automations continue unless the owner separately chooses to pause them.

Resolve friendly product names to the canonical kinds before calling the action: Docs to doc, Sheets or Workbooks to workbook, Slides to slide, Notes to notebook, and Image Projects to imageProject. Report partial validation failures honestly and never claim that enabling an app also completed a resource request.

Related actions

arinova.office_apps.enable

Also known as

office apps, office app installation, install office app, enable office app, add office apps, 辦公應用程式, 啟用辦公應用

---

Machine-readable Markdown · Knowledge index