A chat keeps more than its messages: the decks, presentations and reports it produced stay with it, with the settings and snapshots behind them. This page covers those records, the settings a deck is built with, and the states you may see when a generation cannot run. To build one, see Generate a presentation or slide deck; to find what a Mind saved, see Artifacts.
A deck is built from the settings chosen for it, in the Generate Presentation dialog or on the presentation's card. When a setting was never chosen, the platform's default is used:
| Setting | What it controls | Default |
|---|---|---|
| Content Amount | How much content each slide carries: Brief, Medium, Detailed or Extensive. | Extensive |
| Number of Slides | How long the deck is. | 10 |
| Theme | The deck's look, from the theme catalog. | Borealis |
| Tone & Style | How the deck reads. | Professional and Engaging |
| Target Audience | Who the deck is for. | General Audience |
| Language | The language the deck is written in. | English |
A deck can also carry Custom Instructions you write for it. For the dialog fields and their limits, see Generate a presentation or slide deck; for themes, see Presentation themes.
A generation builds into the deck's own Slides conversation. A run can be refused or stopped, and the message says why:
Each run writes one version of the deck, labelled AI generated, so you can tell where a change came from in Version history; see Saving and version history.
Yes. Every generation is kept. A finished deck is saved as its own artifact, and a chat's presentations keep every version, with the newest one opening by default.
A deck that is built without a chosen value for a setting uses the platform defaults: 10 slides, Extensive content, the Borealis theme, Professional and Engaging tone, General Audience and English. The table above lists what each setting does.
A build and a live editing session would change the same deck at once, so the generation is refused while the deck is being edited. Close the deck in the Slides editor, or wait until nobody has it open, then try again.
Wait for it to finish. One run builds into a deck at a time, and a second one is refused until the first is done. The result appears in the deck's Version history, labelled AI generated.
The deck's own conversation is busy, so a second request cannot start right now. Wait for the current turn to finish, then run the generation again.
The run reached its time limit and stopped; the message reads "The generation turn did not finish within 15 minutes." Open the deck to see what was built, and start the generation again if it needs to go on.
The platform renders decks in a shared environment, and it is busy with other work, so this render did not start. Wait a moment and try again.
The option is decided per person: it appears only when the platform can confirm that you can open the live deck in Slides. If you have no access to the live deck, or it no longer exists, the snapshot opens without the option. Ask the deck's owner for access to the live deck, then open the snapshot again.
Yes. Generating into a deck needs the right to open that deck in Slides. See Slides permissions.
They leave the lists with the chat they belong to. The stored records behind them are soft-deleted, so they are marked as deleted rather than erased.
Each generation writes one version of the deck, and that version carries the label AI generated. Open Version history to find it among the deck's versions; see Saving and version history.