Do you have a package that's become obsolete, perhaps because the project's scope has changed? If so, read this article to learn how to hide them in the Package Register.
As well as packages becoming redundant when a project's scope changes, you might also create a package then find there's a problem with it and it shouldn't be used. Or you might have to recreate a package but hide the original so it isn't accidentally used by others in your organization.
To get around these problems, you can use Mark as No longer in use, which hides them in the Package Register and stops them being used by anyone else. When you do this, they are hidden in the register, and all actions within the package are disabled. This means collaborators can no longer edit the package, nor can they distribute or review it.
Only Package Administrators can mark packages as no longer in use. If the package is part of a hierarchy, all child packages must be marked as no longer in use before you start.
If you mark a package as no longer in use, its state changes to No Longer In Use. And, by default, when you open the Package Register this type of package is not visible. If you want to see packages marked as no longer in use:
