Project 'save in library' feature and usage count

Question

I like to filter by the use count and last used date fields in the library to see which content has not been used for a while.  This worked well for me until I turned on the save in library feature in our projects.  Now my use count for Q&As are rising because of the multiple edits being made in projects.  (Example: One common listing on the Q&A usage info are multiple rows with this used type "Apply(Project-AI)."

I would like to see if a Q&A was used in the creation of a project's answer, and I would like it to count one time for that for that specific use.

Based on my research, if the save in library feature is on, it's going to track everything related to the library's Q&As.

* Do you use the save in library feature? Why? 
* If you use the save in library feature, how do you quickly determine which Q&As in the library are not used often (aside from filtering/using the Utilization report to Q&As with 0 use count)?

I appreciate your input.

Thank you.

Renee Underwood · Answer

Hi @Susan Puckett, thanks for posting in the community! I’m sharing a response here as well, and I’m also going to ping a few folks internally to see if we can get input from another customer who’s run into something similar.

On your specific question around quickly identifying underused Q&As (without relying on broader reporting tools you already mentioned), a couple of the most practical approaches in the Content Library are the filters you called out:

* You can continue to use Use Count as a primary filter, but instead of just looking at “low vs high,” you can set tighter thresholds (for example, 0, 1–2, or whatever range makes sense for your library size) to quickly surface content that’s likely underutilized.
* Pairing that with Last Used Date is usually the most effective way to get a signal beyond the noise you’re seeing from Project AI activity. Even if the use count is being inflated by repeated “Apply(Project-AI)” entries, the last used date can help you understand whether something is actually being surfaced over time or just repeatedly referenced within a narrow project window.
* Additionally, Created Date and Updated Date filters can help you segment older content that hasn’t meaningfully been refreshed or re-engaged with, which often highlights candidates for cleanup or review when combined with low-use indicators.

Your observation about Save in Library impacting usage tracking is a really good one. Can you offer more details on what you've seen for it impacting the used count?

I’ll follow up internally and see if we can get another customer perspective on how they’re handling this as well, since I think there may be some useful practical workarounds people have developed.