Share a Snippet Library With Your Team on Windows

To give a team one set of approved snippets, make one person the owner, keep a master CSV in a shared folder that only the owner can edit, and have everyone import each new version. Import adds the shortcuts a person does not have and skips the ones they do, so a changed text needs one extra step from each teammate.

This guide covers running the library over months: who decides, how versions are named, how updates reach people and how old texts are retired. For a one-off transfer to a colleague or a new computer, see moving snippets to a new PC. For the same library in Chrome and Edge, see sharing snippets across Chrome, Edge and Windows.

Download the team starter file

Download the team snippet starter (CSV). It has 15 entries for company details, support, sales and office messages. Every shortcut starts with ;co-, every row imports disabled, and every value in square brackets is a placeholder.

1. Keep ;co- or replace it in every row with a short abbreviation of your company name.
2. Rewrite each text in your approved wording and delete the rows you do not need.
3. In the rows you approve, change enabled from false to true, so teammates get shortcuts that work straight after import.
4. Save the result as version 1 in the shared folder and import it on your own PC first.

Give the library one owner

Shared snippets drift when anyone can change them. One person owns the master file, usually the team lead or office manager. The owner does not have to write every text, but nothing reaches the file without their check.

Texts about refunds, prices, delivery times or legal terms need sign-off from whoever owns that policy. Record the approver next to the change in the changelog.

Collect requests in one place, such as a team thread or a shared form. A useful request has the proposed shortcut, the full text and the situation where it will be used.

Keep the master file in one shared folder

Team snippets/
  team-snippets-v3-2026-10-11.csv
  CHANGELOG.txt
  archive/
    team-snippets-v2-2026-09-02.csv
    team-snippets-v1-2026-08-05.csv

Put the version number and date in the filename. Teammates can then tell whether the file they last imported is current, and you can roll back by sharing an older one. Keep only the current version at the top level and move older ones to archive.

Give teammates view access and keep edit access for the owner. In OneDrive and SharePoint, Can view lets people view the item but not edit it.

If you maintain the texts inside the app and export them, the export contains every snippet on your PC, personal ones included. Delete those rows before you publish the file.

If you edit the master in Excel, check the saved file before publishing. Excel takes the CSV separator from the list separator in Windows region settings, and a file separated by semicolons will not import: the app reports that the shortcut and replacement columns are missing. Open the file in Notepad, confirm the first line reads shortcut,replacement,enabled,triggerMode, and check that symbols and accented letters look right.

Write the changelog entry before you announce a version. Teammates use it to see what to delete before they import.

v3  2026-10-11  owner: [name]
Added:    ;co-sup-known
Changed:  ;co-hours (new Friday hours, approved by [name])
Retired:  ;co-sales-promo (offer ended)
Before importing: delete your ;co-hours and ;co-sales-promo

Name team shortcuts with one prefix

Every team shortcut starts with the same prefix, and personal shortcuts never use it. The prefix shows which entries came from the team file and keeps personal and team shortcuts from sharing a name. A clash matters, because import keeps whichever version is already on the PC.

Use lowercase only. ;co-Hours and ;co-hours count as two different shortcuts, so a change of capitals arrives as a duplicate instead of an update. Shortcuts cannot contain spaces and can be up to 64 characters long. The shortcut naming guide covers choosing names people remember.

Never reuse a retired shortcut for a different text. Anyone who missed the deletion would keep the old text under a name the rest of the team now uses for something else.

What happens when a teammate imports a new version

Import compares shortcuts, not texts. Each row in the file is handled like this:

When the import finishes, the app shows how many entries were imported and how many were skipped. It does not list which ones.

If a teammate wants their own variant of a team text, they should save it under a personal shortcut. Editing the team entry in place means they keep the edited copy and miss later updates to it.

Roll out a new version

The owner saves the new file, writes the changelog, runs the steps below on their own PC and then announces the version with its filename and the list of shortcuts to delete. Each teammate then does this:

1. Export the library to a backup file.
2. Delete your copy of every shortcut listed under Changed and Retired.
3. Import the new file.
4. Compare the imported number with the changelog. It should equal the Added count plus the Changed count: 1 + 1 = 2 for version 3 above.
5. Expand a changed shortcut in an unsent draft and check the new text.

A lower number means a shortcut you meant to delete is still there. Find it, delete it and import the same file again. Everything else is skipped, so a second import is safe. A higher number means the file brought back team shortcuts you had deleted earlier; delete them again if you do not use them.

Retire snippets on purpose

Deleting a row from the master stops new imports from adding it. It does not remove the snippet from anyone’s PC. Each teammate deletes it, so list every retired shortcut in the changelog and in the announcement.

When a text is retired because it became wrong, such as an old price, a closed office or a changed refund rule, say so in the announcement. A stale copy keeps expanding until its owner deletes it, and it reads as current to the customer who receives it.

Keep secrets and personal data out

The master file is plain text. Anyone with access to the folder can read it, and each import copies its contents into another library on another PC, where they stay after you correct the master.

• Passwords and access codes, including the guest Wi-Fi password and door codes.
• API keys, tokens and recovery codes.
• Bank details. A wrong or altered account number in a shared text sends a customer’s payment to the wrong place. Keep payment details in your invoicing system.
• Customer data: names, email addresses, order details or anything copied from a ticket.
• Colleagues’ personal phone numbers and home addresses.

Use placeholders such as [customer name] and [order number] instead. Before publishing a version, search the file for @, long runs of digits and the word “password”.

Review the library on a schedule

Support texts go out of date fastest, so review support snippets monthly, as the customer support snippets guide suggests, and the rest at least once a quarter. Review out of turn whenever a price, policy, product name, opening hours, link or contact person changes.

• Open every link in the file.
• Check names, hours, prices and contacts against their current source.
• Ask the team which shortcuts they have not used since the last review, and retire those.
• Merge shortcuts that now say nearly the same thing.
• Answer the open requests, even when the answer is no.

Frequently asked questions