Gamma's current Agent can turn notes into a presentation through a Plan step: it asks questions, shows an outline, and waits for approval before building. That pause gives a presentation owner a place to catch missing evidence before the deck exists. The harder check comes afterward, when every card and the eventual viewer's permissions need review. This guide follows Gamma's documentation checked on 20 October 2026. BIG CHANGE did not sign in, generate a deck, test a recipient link or measure time or credit use.

The reader is a presentation owner allowed to send approved notes to Gamma and share the result. The intended output is an editable deck in Gamma and a browser link that an intended recipient can open to view, without editing. You need an account that offers the current Agent and Plan controls, enough credits for the actions you choose, approved source notes, a defined audience, and authority over the deck's sharing scope. Availability and permissions depend on the actual account and workspace.

The big change

Gamma's current Agent creation flow puts a reviewable plan between the initial request and the build. The owner can use that checkpoint to keep the proposed story within approved notes, then correct the generated cards by hand or with targeted Agent requests. A finished deck still needs two separate judgments: whether its claims and visuals are supported, and whether the actual recipient has only the intended access. Gamma's sharing guide says workspace permissions can override a deck's link setting.

Prepare the source and the request

  1. Set the source boundary. Keep a copy of the approved notes outside the deck. Mark each number, date, quotation, attribution and material claim so you can locate its source during review. Remove anything your organization or the source owner has not authorized for Gamma cloud processing. Decide who should see the result before uploading material or enabling a link.
  2. Start in Plan. From Gamma's dashboard prompt bar, describe the presentation's audience, purpose and intended length. Paste the permitted notes or attach an authorized file. A useful request in ordinary language is: "Make a short presentation for the named audience using only these approved notes. Keep the cited figures and dates attached to their source. Flag gaps or uncertain claims for my review instead of filling them in. Show me the plan before building." Adjust the audience and length to the real assignment. Select Plan in the mode picker. Gamma says Plan asks questions and waits for approval; on a mobile browser, Express may be selected by default, so check the picker. Leave Research off for a deck confined to approved notes. If you enable it, verify any added web claims separately; Gamma says Research works with Plan.
  3. Approve a source-bound plan. Answer the Agent's questions with the real audience and purpose. Compare its proposed sections and story order with the notes. Remove unsupported claims, unapproved comparisons and any section that promises evidence you do not have. Ask for a revised plan until its outline has a source for each substantive point, then give the go-ahead to build. Approval of the plan is a content decision, not proof that the later cards will be accurate.

Review every card before sharing

  1. Check the generated deck card by card. Open each card and compare its material text, figures, dates, quotations, image implications and attributions with the approved notes. Check that no generated illustration looks like documentary evidence of an event it does not show. For a mismatch, edit the card directly or ask Agent for a specific correction, such as fixing one number from its cited source. Reopen the changed card and compare it again. Gamma documents both direct editing and targeted Agent changes; neither removes the owner's duty to check the result.
  2. Read it as the audience will. Move through the complete deck in order. Check missing or duplicated cards, labels, contrast, image crops, overflowing text and legibility in presentation mode. Confirm the opening tells the intended audience what the deck covers and the ending does not claim more than the notes support. Keep unresolved claims out of the shared version. This is a proposed human review procedure, not a result BIG CHANGE observed.

Set access and test the actual link

  1. Inspect both permission paths. Open Share and review Anyone with the link and Workspace members separately. Gamma lists No access, View, Comment and Edit levels. Choose View only for a scope you are authorized to share with. An anyone-with-link setting allows whoever holds that link to use its granted access; it is not a named-recipient restriction. If access must stay within a named or workspace audience, keep the broader link route closed and use only the authorized sharing route that the account actually offers. Gamma says workspace settings can give members editing rights even when a deck link is set to View. If those rights exceed the intended scope, have the owner or authorized administrator resolve them before sharing. Do not alter wider workspace permissions without authority.
  2. Verify from the recipient's side. After the content and access scope are approved, copy the link and open it in an authorized recipient context. Ask the intended recipient to confirm they can open the complete deck, read the cards in order and cannot edit through the access provided. A test in the owner's signed-in browser does not establish the recipient's permissions. If the recipient cannot open it, check their actual role and the two sharing paths; do not make the deck public as a troubleshooting shortcut. If they can edit unexpectedly, stop distribution and inspect workspace rights as well as the deck setting.

The task is complete only when the owner has checked every card against the notes and the intended recipient has confirmed the browser link works with the intended view access. A View link removes Gamma's built-in export controls for viewers, according to the sharing guide, but it does not stop browser printing or saving through the browser. Treat the deck's contents as disclosed to anyone who can actually view it.

Credits, limits and another presentation route

Gamma's credit guide says a new Free user receives 400 initial credits that do not refresh. Presentation creation is metered by slide and image; Agent edits and other AI actions can use credits. The amount varies with the action, model and generation complexity, so there is no fixed cost for this deck. Check the account's balance before starting and any displayed image-model cost before generation. Paid plan allocations refresh monthly. If the required AI action is unavailable or credits run out, pause and choose an authorized account, plan or manual editing route. The current Agent/Plan instructions should not be replaced with the older classic generator's steps.

This procedure produces a Gamma browser deck and checked view link. Gamma documents a separate export workflow for PDF, PNG and PowerPoint files. An exported file needs its own inspection in the target app and is outside this completion check. For a local HTML slide deck, see our local creation and export guide. Our guides to adding a checked section to an existing PowerPoint and building a PowerPoint deck from checked PDF evidence address different inputs and outputs.

Sources & further reading