In this Page

Overview

The Snap Packs page within a project lists the Snap Packs explicitly added to that project. Snap Packs added to the shared project are accessible to all users, while those added to another project are only available within that project.

Hover over the Snap Pack name to access the context menu. From there, you have access to view the Snap Pack's activity log to see when it was created or modified.

Behavior Change

In versions before 4.33, Snaps from a private Snap Pack uploaded to a Project, the Project shared folder, or the Global shared folder were accessible within the Project. However, the latest update has modified this behavior. Now, when you upload a Snap Pack to the Project space containing Snaps different from those uploaded to a shared folder, only the Snaps directly uploaded to the Project will be visible. Refer to the example below for a better understanding of the behavior change.

Your existing Pipelines utilizing Snap Packs might no longer be accessible because of this update and will require fixing. To resolve this issue, ensure that you upload the required Snaps directly to your Project folder for the Pipelines to function as expected.

Private Snap Packs

You can upload Private Snap Packs to the following folders:

• Project folder within Project Space: When working on a project, you can create a specific folder dedicated to that project. This folder is located within a designated area called the Project Space.

• Shared folder within Project Space: Within the Project Space, you can have a folder shared among multiple users working on the project. It allows those users to access and collaborate on the files within that folder.

• Global Shared folder: This refers to a shared folder across different projects or spaces. It is accessible to users in various projects.

If you create a pipeline within a specific project folder, you can only see the Snap Packs uploaded to that specific project folder. However, if the pipeline is created in a shared folder within the Project Space or in a Global Shared folder, you may have access to a wider range of snap packs from different Projects or Project Spaces. Essentially, the folder location in which you create a pipeline determines the scope of visibility for the Snap Packs in the pipeline. Refer to the examples below for better understanding.

Examples

Most scenarios can be categorized within the examples mentioned below when creating pipelines and determining Snap Packs' visibility.

Example 1

If you have Snap Pack A and B uploaded to the following locations,

• Global shared: Snap Pack A (Snap A-1, Snap A-2)

• Project space shared: Snap Pack B (Snap B-1, Snap B-2)

• Project: Snap Pack B (Snap B-1, Snap B-3)

The visible Snaps in the Project folder are Snap A-1, Snap A-2, Snap B-1, and Snap B-3 (Snap B-2 is not visible because it is not uploaded to the Project).
The visible Snaps in the Project space shared folder are Snap A-1, Snap A-2, Snap B-1, and Snap B-2.
The visible Snaps in the Global shared folder are Snap A-1 and Snap A-2

Example 2

If you have Snap Pack B uploaded to the following locations.

• Global Shared: Snap Pack B (Snap B-0, Snap B-1)

• Project Space Sshared: Snap Pack B (Snap B-1, Snap B-2)

• Project: Snap Pack B (Snap B-1, Snap B-3)

The visible Snaps in the Project folder are Snap B-1, and Snap B-3.
The visible Snaps in the Project space shared folder are Snap B-1, and Snap B-2.
The visible Snaps in the Global shared folder are Snap B-0 and Snap B-1.

Example 3

If you have Snap Pack A and B uploaded to the following locations.

• Global Shared: Snap Pack B (Snap B-0, Snap B-1)

• Project Space Shared: Snap Pack B (Snap B-1, Snap B-2)

• Project: Snap Pack A (Snap A-1, Snap A-2)

The visible Snaps in the Project folder are Snap A-1, Snap A-2, Snap B-1, and Snap B-2.
The visible Snaps in the Project Space Shared folder are Snap B-1, and Snap B-2.
The visible Snaps in the Global Shared folder are Snap B-0 and Snap B-1

Related Content:

• Snap Packs (Org Level)

• Removing a User from an Org