This site has moved to the integrated Appfire documentation and information site for our apps.

From February 2024 this site is no longer updated.

Take a look here! If you have any questions please email support@appfire.com

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Current »

Snapshot Publishing

Snapshot Publishing is used to create a static copy of a Confluence document at a specific moment in time.

Snapshot documents can be organized and shared by adding to one or more snapshot collections.

Each collection can be shared to any users or user groups who are given viewing permission by the creator of the collection - the collection manager. Users can be given permission to contribute snapshots to a collection.

Snapshots can be added to a collection from one or more spaces across the instance. Space administrators can link a collection to their space to allow users in their space (who are contributors to the collection) to add snapshots from the space.

Snapshot publishing does not require a space separate to the source Confluence space. Snapshots are stored linked to the space in which they are created but are viewable through the collections global viewer.

Viewers only have access to items they need through each themed collection, for example for use as manuals/handbooks. They no longer need access to the content in a draft space.

If a Comala Document Management workflow is applied to a document, snapshot publishing can be configured to occur on a workflow event using a workflow trigger.

Who can create a snapshot of a space page or blog post?

To snapshot publish a space document you need

You also need to be added as a collection contributor to at least one snapshot collection.

Snapshot publishing status

A Confluence page will display a snapshot publishing status byline (if snapshot publishing is enabled for the space).

The snapshot publishing byline can be used to open the snapshot publishing popup to create a snapshot and add it to one or more snapshot collections.

The byline is updated to display the current snapshot publishing status for the document.

The popup content is also updated to display

  • the current snapshot publishing status

  • the last snapshot creation date

  • the user who created the snapshot

  • the collections the snapshot is currently added to

A View button is added. This opens the global collection viewer to display all the collections that the current user is able to either view (has been given collection viewer permission) or contribute a snapshot (has been given collection contributer permission).

Managing snapshots in a collection

Snapshots can be organized and shared by creating a Collection and adding chosen snapshots to a Collection. A snapshot can be added to one or more different Collections.

The creator of a Collection (the Collection Manager) can manage the users and usergroups who can

  • view the Collection

  • contribute a snapshot to the Collection

Users who can create a collection must be a space administrator and also added as a member of the Confluence user group added to the global snapshot configuration dashboard.

Snapshots can be added to a collection from any space if

  • the collection is linked the space

  • a user has been contributor permission for the collection

To link an existing collection created in another space, the space administrator must have at least contributor permission for the collection.

Collections can be viewed in Confluence using a Collection global viewer accessed through the Confluence top header menu. Each page snapshot is displayed in pdf or html format.

Snapshot User Guide

Filter by label

There are no items with the selected labels at this time.

Snapshot Publishing Guide

Filter by label

There are no items with the selected labels at this time.

Space content can also be copied to another space in a one-off copy action using Copy Space. The target space set for Copy Space is not linked to the target space set in the copy space configuration for the space.

  • No labels