Keep button in the Obsolete content View

Sheldon Matos

I'm submitting this S4 on behalf of Securiguard Services:

Hi Sheldon,
The advice provided below does not directly address my core question about how to keep documents from the Obsolete Content view tab directly. Could you please confirm whether the platform currently has no option to “keep” documents directly from the Obsolete Content view? The suggested workarounds seem to highlight the inefficiency of the current process, as they require me to first assign all 169 documents to myself and only then gain the ability to keep them, which is not scalable, if I understood it right. The “on‑demand review” form mentioned in the snippet is not visible in my instance, and I’m unclear why this extra step would be required when the Obsolete Content section under Documents has already collected all items that need review. As previously noted, editing an item (for example, changing an image document’s name or making a minor update) does not remove it from the Obsolete list in my environment, so this remains an ineffective workaround, as well as time-consuming. If there truly is no efficient way to handle this from the Obsolete Content view, could your team prioritize deploying a “Keep” button or similar control within that view, so users can quickly reclassify selected documents as non‑obsolete without reassignment or per‑item edits?

sathish s

@Sheldon Matos

Introducing a “Keep” button for individual documents—or as a bulk action within the Obsolete Content view—would undermine the purpose of the review process.

A document is marked obsolete because it has not been updated or its required review has not been completed within the configured review period. Simply allowing users to remove documents from the Obsolete Content view without completing the prescribed review would bypass the intended governance workflow and weaken accountability.

To maintain content accuracy and auditability, documents should be removed from the Obsolete Content view only after the required review has been completed and the document has been formally confirmed, updated, or approved through the appropriate workflow.