Audit and archive unused snippets

A shared snippet library only grows. Nobody can say which snippets are still in use, so nobody deletes any, and the picker keeps getting longer. The Usage tab in Settings → Snippets answers the “is anyone using this?” question directly, and lets you retire the snippets that aren’t — without deleting anything outright.

Before you start

• The Usage tab is only visible if you can manage global snippets. If you don’t see it next to your snippet list, you don’t have that permission.
• It covers shared (global) snippets only. Personal snippets belong to the agent who wrote them, so nobody else audits or retires them — that includes any personal snippet marked as an email signature, since the composer inserts a signature without recording a use, which would make it look permanently unused.
• Usage counting started the day this feature was deployed. A snippet that’s existed for years but hasn’t been used since the deploy will show 0 uses until someone uses it again — the page tells you this. Don’t read “0” as “nobody has ever used this.”

Read the usage list

1. Open Settings → Snippets → Usage.
2. Every shared snippet is listed with:
   Last used — how long ago it was last inserted into a reply.
   Last 30 days — how many times it’s been used in the trailing 30 days.
   Total uses — the running total since usage tracking began.
3. Click a column header to sort by it. The list defaults to sorting by total uses, so the least-used snippets are easy to find by flipping the sort direction.
4. A snippet with no recorded use shows a dash or zero, not an error — it either hasn’t been used since tracking began, or it’s genuinely never been used.

Preview and archive unused snippets

1. Choose Archive unused and enter the number of days that defines “unused” (for example, 90).
2. The dialog previews the result before anything is written: it tells you how many snippets match — snippets with no use recorded inside that window — rather than listing every title in a scrolling panel. If you want the detail, it’s in the Archived list after the fact.
3. The window can’t exceed the tracked usage history. Because tracking starts at deploy time, a window longer than the history available would flag every snippet as unused just for being older than the tracker — so the action refuses and tells you how many days of history actually exist. Shorten the window and try again.
4. A snippet younger than the window you chose is left alone rather than swept up — it never had the full window in which to be used.
5. Confirm to archive. There’s no success toast: the confirmation is the snippet disappearing from the active list. If the archive fails, you’ll see an error.

An archived snippet is removed from every place a shared snippet would normally show up — the snippet picker, shortcode expansion, the titles and categories lists, sidebar group counts, favorites, recent snippets, and the public API. It can’t be opened, used, favorited, or have its attachment copied into a conversation while archived; each of those now returns a 404.

Restore an archived snippet

1. Switch to the Archived view within the Usage tab.
2. Find the snippet and choose Restore.
3. It’s immediately available again everywhere a shared snippet normally appears — the picker, shortcode expansion, categories, and so on — exactly as if it had never been archived.

Restoring, like archiving, doesn’t pop a success toast — the snippet leaving the Archived list and reappearing in the active list is the confirmation.

Limitations

• Shared snippets only. Personal snippets, including personal signatures, never appear in the Usage tab and can’t be archived from here.
• Usage counting starts at deploy. A snippet’s total and last-used date only reflect activity since this feature shipped — earlier history isn’t retroactively counted.
• The archive window is capped by tracked history. You can’t request “unused in the last 90 days” if the tracker has only been running for 30 — the action tells you the real ceiling and refuses anything past it.
• A snippet newer than the window is excluded, not treated as unused, since it never had the full window available to be used in.