An agent turns an internal planning deck into a polished customer presentation. The visible slides look right. The user approves the preview, and the agent prepares to share the original PowerPoint file.

That last step deserves its own review. A slide preview shows the intended presentation surface, not necessarily everything distributed inside the editable artifact.

For teams sending agent-generated presentations outside their original audience, the practical deliverable is a release copy with an explicit content boundary. Keep the working deck intact, decide what recipients need, and inspect the file that will actually leave the team.

Methodology and audience

We reviewed Microsoft's documentation on hidden slides, Document Inspector and PDF export on September 24, 2026. The workflow below is an editorial recommendation built around those documented distinctions.

We did not create a sample deck, execute an inspection, or certify any presentation skill. This guide is for people preparing external handoffs; it is not a claim that every generated PPTX contains sensitive material.

Our selection criterion was distribution risk rather than visual quality. Font portability and editability remain important, but neither establishes that all included information is appropriate for the recipient.

Hidden is a presentation setting, not deletion

Microsoft explicitly documents that a hidden slide remains in the presentation file and is merely omitted from the normal slide show. Hide or show a slide.

Consider a fictional deck with twelve customer-facing slides and three hidden pricing alternatives. If only the twelve slides are approved for distribution, hiding the alternatives does not fulfill that instruction.

Our recommendation is to create a separately named release copy and use an approved slide list. Record slide titles or stable identifiers as well as numbers, because numbers can shift during editing. Remove excluded slides from the release copy only after confirming that this is the intended handoff.

Preserving the private working version matters. “Make this safe to share” should not become permission to destroy the team's source material or eliminate context needed for future revisions.

Decide what the recipient is allowed to receive

Before inspection, write a short distribution brief:

The intended audience and delivery channel.
The slides and supporting materials approved for that audience.
Whether speaker notes should be included.
Whether recipients need editable charts, source data or only rendered views.
Who must resolve an uncertain inclusion.

This is an allowlist, not a promise that every possible hidden feature has been enumerated. It prevents a common ambiguity: the designer assumes only the visible chart will travel, while the next editor expects its underlying data to remain available.

Ask the owner to decide that trade-off. Do not silently flatten every object or strip all notes just to obtain a cleaner report; those operations can remove functionality that the recipient was promised.

Use Document Inspector, but read its exceptions

Microsoft recommends inspecting a copy because removed information may not be recoverable. Its PowerPoint guidance covers items including comments, personal properties, invisible content and presentation-note text. It also identifies limitations: pictures in Notes are not removed, covered objects are not detected by the invisible-content check, and certain embedded items require manual decisions. Microsoft Document Inspector guidance.

Our proposed review record separates three outcomes: checked and acceptable, changed and rechecked, or unresolved. “Inspector ran” is not an adequate fourth outcome.

For each flagged item, compare it to the distribution brief. Keep necessary content only when its inclusion is understood. When the agent cannot inspect an embedded object or the required application is unavailable, mark that check incomplete and route it to a reviewer.

Avoid publishing confidential excerpts in the review log. A useful record can identify an object and its disposition without copying its contents into a broadly shared issue or chat.

Choose editable and static deliveries separately

An editable deck and a PDF solve different handoff needs. Neither should be accepted solely because the other looks correct.

Microsoft's Windows PDF export instructions expose choices such as slide ranges and inclusion of hidden slides, comments and document properties. The same documentation describes different options across Windows, macOS and web versions. PowerPoint PDF export.

Our recommendation is to record the actual application and selected export options, then reopen the resulting PDF. Confirm the intended pages and inspect the output's content instead of assuming the file extension is a sanitization guarantee.

For editable delivery, reopen the final PPTX as a recipient would. Check the approved slides, notes and objects against the brief. If the recipient only needs a viewable presentation, do not bundle the private working deck “just in case.” If editing is required, document any data or objects deliberately removed and the resulting limitations.

A non-sensitive rehearsal catches process gaps

Build a small internal practice deck using fictional information. Put an obvious marker on a hidden slide, a different marker in note text, another in a note image, and a harmless extra value inside an embedded object.

Write down which markers are permitted in the release copy before asking an agent to prepare it. Then inspect the actual deliverable and compare the review record with what remains.

The proposed exercise tests whether the workflow knows the difference between what was visible, what was inspected and what was removed. It is not proof that a production deck is free of every disclosure risk. We have not run this exercise for a listed skill.

Also test a requirement to retain one approved note. A process that deletes everything indiscriminately may avoid one mistake while failing the user's intended deliverable.

Limitations and release approval

Office versions, third-party exporters, linked resources and specialized objects can require additional review. An inspection report is not a security certification or a substitute for the organization's information-handling policy.

Keep approval attached to the final release artifact, not an earlier screenshot. Record its identity, recipient scope, approved inclusions, unresolved findings and reviewer. If the file changes afterward, revisit the checks affected by that change before sharing it.

Our editable-PPTX acceptance guide covers the recipient's ability to revise the deck. Use the skill directory to find presentation workflows, then evaluate both boundaries: can the recipient edit what they need, and are they receiving only what the owner intended?