Collections
5.1 Understanding Collections
Collections are a way to organize scripts into groups. Think of them like folders or tags.
Key Features:
- Scripts can belong to multiple collections (like tags)
- Collections are top-level only (no nesting/sub-collections)
- Two types of collections:
- My Collections: Personal, private to you
- Team Collections: Shared with organization members (org workspaces only)
5.2 Creating a Collection
Creating a Personal Collection (My Collections)
- In the sidebar, find My Collections under "My Space"
- Click the + (plus) button next to "My Collections"
- Enter a Name (required)
- Click "Create"
- Collection appears in your personal collections list
Creating a Team Collection (Organization Workspace)
- In the sidebar, find Team Collections under "Shared in [Org Name]"
- Click the + (plus) button next to "Team Collections"
- Enter a Name (required)
- Click "Create"
- Collection is visible to all organization members
Edge Cases:
- Collection names must be unique within their scope (personal or team)
- Collections are created empty (add scripts after creation)
- Free plan users: Cannot create collections (upgrade prompt)
5.3 Adding Scripts to Collections
From Script Editor
- Open a script
- In the editor, look for "Add to Collection" or collection selector
- Select one or more collections
- Script is added to selected collections
From Collection Page
- Open a collection
- Click "Add Script" or "Add to Collection"
- Select scripts from the list
- Scripts are added to the collection
Edge Cases:
- A script can be in multiple collections simultaneously
- Adding a script to a collection doesn't remove it from "All Scripts"
- If you remove a script from a collection, it remains in other collections and "All Scripts"
5.4 Managing Collections
Viewing Collections
Collections are accessible via the sidebar navigation:
My Collections (under "My Space"):
- Shows your personal, private collections
- Access via
/collections-list?type=personal
Team Collections (under "Shared in [Org Name]"):
- Shows organization-wide collections
- Access via
/collections-list?type=workspace - Only visible when in an organization workspace
Each collection displays:
- Name
- Script count
- Nested under the appropriate section in sidebar
Editing a Collection
- Open a collection
- Click "Edit" or collection settings
- Change the name
- Toggle starred status
- Save changes
Deleting a Collection
- Open a collection
- Click "Delete" or collection settings → Delete
- Confirm deletion
- Important: Deleting a collection does NOT delete the scripts
- Scripts remain in "All Scripts" and other collections
Edge Cases:
- Deleting a collection removes scripts from that collection only
- If a script was only in the deleted collection, it appears in "All Scripts"
- Shared collections: If you delete a collection you shared, users lose access
5.5 Sharing Collections
Sharing with Organization Members
- Open a collection
- Click "Share" or collection settings
- Select organization members to share with
- Choose "View only" or "Edit" permission
- Shared users can see all scripts in the collection
Edge Cases:
- Sharing a collection grants access to all current and future scripts in that collection
- If you remove a script from a shared collection, users lose access to that script (unless they have other access)
- Collection permissions are the union of all collections a script belongs to (if script is in multiple shared collections, user gets highest permission level)
5.6 Collection Scripts View
When viewing a collection:
- See all scripts in that collection
- Same search, filter, and sort options as main script list
- Can remove scripts from collection
- Can add more scripts to collection