A share pack is not a wiki, and not a marketplace

You have a finished set of replies for one person, not for the open web.

Right-click a group or a snippet, make a share pack, or copy a deep link that opens the app. They click. The main window comes forward. A confirm dialog runs first. Only then does it write into their local library. That is a packed copy. It is not one wiki page. It is not a public marketplace.

Whoever you send it to can see it. There is no publish page that is readable without an account and without the app.

A contractor who needs this week’s replies, or a home machine that is not on official cloud: use a pack. A ten-person support team that must stay on one returns paragraph: do not keep shipping packs. That is organization groups. Do not mash the two handoffs into one product.

How you hand one over

1. In the main window, right-click a group or snippet and generate the pack or the link. Settings → Data can import too. See Share pack.
2. Send the file or the link. A link that is too long is rejected; split the set or send a file.
3. If they already have the desktop app, the link raises the confirm dialog. Nothing writes until they agree. Free tier stops at 50 snippets / 5 groups; they need a slot first.
4. After import, scan colliding abbreviations. If they already have the same short name, rename before anyone expands. Hygiene.

After it lands, the two libraries walk apart. You change a signature; theirs does not move. They edit their copy; nothing writes back to you. That is the “not a wiki” part: there is not one body two people edit at once.

If a pack carries organization snippets, they still choose Copy to my library before it becomes an editable personal copy. A share pack is not the ACL for organization groups. Ongoing sharing is Team seats and sync. A one-time handoff is a pack. Contrast Team copy.

“One-click import” means the link opens the app and the confirm is the only extra click. It does not mean the pack silently merges into a company catalog. If they decline, their library is unchanged. If they are on free and over the cap, the write fails; the dialog is the place that says so.

Use a pack when a contractor needs this week’s reply set and will not join the org. Use a pack when you send yourself a group to a home machine that is not on official cloud. Do not use a pack as the way a ten-person support team stays in lockstep — that is the other article.

Do not

• Do not treat this as a public snippet marketplace. There is no square, no anonymous catalog.
• Do not treat this as live sharing. What left your machine is a copy, not one lock.
• Do not skip the confirm dialog. No agreement, no new rows.
• Do not smash the whole library into one oversized link and blame the app for refusing it.

Next: pick a group you actually intend to send, export it, and confirm the dialog on a second machine that already has the app.