Astonish

Appearance

Sharing Slides ​

In platform mode, presentations can move between personal and team scopes. Publishing and forking create independent copies so private work and shared work remain clearly separated.

Scope Model ​

Saved decks use two scopes:

  • Personal — visible in your private Slides library.
  • Team — available to members of the current team.

Platform and organization scopes apply to shared slide templates, not to saved decks.

Publish a Personal Deck ​

Use Publish to Team to copy one of your saved personal decks into the current team:

  1. Open Slides in platform mode.
  2. Find the deck in the Personal section.
  3. Open its actions and select Publish to Team.
  4. Confirm the success notification and locate the copy in Team.

You must be authenticated, belong to the current team, and have access to the personal source deck.

Fork a Team Deck ​

Use Fork to Personal when you want your own editable copy of a team presentation:

  1. Find the deck in the Team section.
  2. Open its actions and select Fork to Personal.
  3. Locate the new copy in Personal.
  4. Open it directly or select Enhance with AI to continue refining it in Chat.

Independent Copies ​

Publishing and forking copy the complete deck into the destination scope. The source and destination then have separate ownership and histories:

  • Editing or deleting a personal source does not update the published team copy.
  • Editing a personal fork does not change the team deck.
  • New versions belong only to the copy being saved.

To share later changes, publish the intended updated deck according to your team's naming practices.

Name Conflicts ​

A publish or fork operation cannot replace an existing destination deck with the same permanent identifier. If Studio reports a conflict, rename or save the source as a distinct deck before trying again, or remove the conflicting destination deck if it is no longer needed and you are allowed to do so.

Permissions and Availability ​

Publish to Team and Fork to Personal appear only in platform mode and only for the appropriate source scope. Team membership and tenant boundaries determine which decks are visible and which destination is used.

For the general sharing model across Astonish resources, see Publish & Fork.

Next Steps ​