---
{
  "id": "platform.slide.decks-and-lifecycle",
  "topic": "slide",
  "title": "Slide deck creation, access, archive, and deletion",
  "locale": "en",
  "version": "2026-09-05.1",
  "summary": "Deck Actions atomically create a presentation with its supplied slides, expose only the current owner-and-Agent-grant scope, and require archive before confirmed deletion.",
  "content": "`create_deck` requires a complete ordered `slides[]` with each slide title and content. It atomically creates the deck and supplied slides; an explicit writable `spaceId` targets a shared workspace. Deck metadata is title, description, theme, defaultAspectRatio, and archived state. The aspect ratio supports only `16:9` or `4:3`. Theme has a strict `backgroundColor` and `fontFamily` allowlist: an unknown key returns `invalid_arguments`, unlike forward-compatible element extension keys. The executing Agent receives the deck grant used by later Actions. `get_deck` returns deck metadata; use `list_slides` for ordered bodies.\n\n`update_deck` changes only supplied metadata; omission cannot clear description. Archive is reversible: use `archive_deck` and `unarchive_deck`; `list_decks` hides archived decks unless `includeArchived` is true. Both lifecycle Actions preserve Agent version attribution and invalidation events. The list intersects triggering-user document visibility with Agent owner identity and either a direct permission row or qualifying Space grant; personal decks must be owned by the triggering user. Grants are product-managed, not self-issued. Runtime applies the same read/write intersection and reports failures as `permission_denied`.\n\n`export_deck` accepts only PDF, resolves ready managed images from the same deck without fetching external URLs, and saves through the personal File Center pipeline. Dry-run performs access validation but creates no file. `delete_deck` is irreversible: the deck must already be archived or runtime returns \"must be archived before deleting\"; UserConfirm is required, and all slides, image bindings, and Slide version history are purged, so restore or copy cannot recover it. To preserve content, preview, `copy_version`, or `export_deck` before archiving; history mutations are read-only while archived, so temporarily unarchive before copying if necessary. If the user only wants reversible hiding, archive instead of deleting.\n",
  "aliases": [
    "create presentation",
    "list decks",
    "archive deck",
    "delete presentation",
    "deck permissions",
    "deck lifecycle"
  ],
  "tags": [
    "slide",
    "deck",
    "lifecycle",
    "permissions",
    "archive"
  ],
  "relatedActions": [
    "arinova.slide.create_deck",
    "arinova.slide.list_decks",
    "arinova.slide.get_deck",
    "arinova.slide.update_deck",
    "arinova.slide.archive_deck",
    "arinova.slide.unarchive_deck",
    "arinova.slide.export_deck",
    "arinova.slide.delete_deck"
  ],
  "relatedActionPrefixes": [],
  "url": "https://docs.arinova.ai/en/kb/slide/decks-and-lifecycle/"
}
---

`create_deck` requires a complete ordered `slides[]` with each slide title and content. It atomically creates the deck and supplied slides; an explicit writable `spaceId` targets a shared workspace. Deck metadata is title, description, theme, defaultAspectRatio, and archived state. The aspect ratio supports only `16:9` or `4:3`. Theme has a strict `backgroundColor` and `fontFamily` allowlist: an unknown key returns `invalid_arguments`, unlike forward-compatible element extension keys. The executing Agent receives the deck grant used by later Actions. `get_deck` returns deck metadata; use `list_slides` for ordered bodies.

`update_deck` changes only supplied metadata; omission cannot clear description. Archive is reversible: use `archive_deck` and `unarchive_deck`; `list_decks` hides archived decks unless `includeArchived` is true. Both lifecycle Actions preserve Agent version attribution and invalidation events. The list intersects triggering-user document visibility with Agent owner identity and either a direct permission row or qualifying Space grant; personal decks must be owned by the triggering user. Grants are product-managed, not self-issued. Runtime applies the same read/write intersection and reports failures as `permission_denied`.

`export_deck` accepts only PDF, resolves ready managed images from the same deck without fetching external URLs, and saves through the personal File Center pipeline. Dry-run performs access validation but creates no file. `delete_deck` is irreversible: the deck must already be archived or runtime returns "must be archived before deleting"; UserConfirm is required, and all slides, image bindings, and Slide version history are purged, so restore or copy cannot recover it. To preserve content, preview, `copy_version`, or `export_deck` before archiving; history mutations are read-only while archived, so temporarily unarchive before copying if necessary. If the user only wants reversible hiding, archive instead of deleting.