What We Fixed
Once a template or automation lived in the library, there was no way for the submitting team to remove it without asking a platform admin to archive it on the backend. This applied equally to community submissions and to private/team-shared items in your own library.
What Changed
- My Library Items (new page at
/library/my-items): lists the personal and team-shared templates and automations you’ve added to the library. Each item has Archive and Restore controls so you can hide and restore items yourself. Restoring a never-public item returns it straight to your library — no admin review needed. - My Submissions: approved and rejected community submissions have an Archive action. Archiving an approved submission keeps it in My Submissions marked Archived with a Resubmit for Review action that sends it back to the admin queue. Archiving a rejected submission moves it to My Library Items, where Restore puts it back into the admin queue (community content always goes through admin review). Existing copies on other teams keep working — archive only stops further discovery and copying.
- Admin submissions queue: platform admins can archive any community submission directly from
/admin/library/submissions, alongside the existing approve/reject actions. A new Archived status filter lets admins find and re-review previously archived items. - Pending submissions still use Withdraw, which deletes the draft outright since nothing downstream depends on it yet.