What Changed
Getting a starter pack’s content into a collection used to be a manual relay:
install the pack, then share each installed automation and template back to your
library one by one, then add each of those items to the collection. For a
corporate team assembling the collection its branches would receive, that was a
dozen-plus clicks per pack.
Now it’s one click, from either direction:
- From a collection — open it and hit Import Starter Pack, pick a pack,
and its items are copied into your team and added to the collection. - From a starter pack — the pack page has a new Add to a collection
button next to Install.
The imported items belong to your team, so you can edit them (rename them, adjust
the copy, retune an automation) before anyone else installs them.
Designate the collection as your enterprise packet
Collection Share now has a Use as the enterprise packet toggle for owners
and admins of an enterprise’s corporate team. Turn it on and every branch under
that enterprise can install the collection, and newly created branches get it
automatically.
When the pack changes later
The collection remembers which pack each item came from. If an admin updates the
pack afterwards, the collection page says so — “2 have updates in the pack” —
with a Re-import button that pulls the newer versions down.
Good to know
- Re-importing replaces the items that the earlier import created, including
edits you made to them. Items you added to the collection by hand are never
touched. - Importing the same pack twice never creates duplicates.
- Items an admin has since archived or moved out of the official library are
skipped, and the import tells you which ones and why. - Importing into a public, already-approved collection sends it back to private
draft for admin re-review, the same as adding any other new item to it.