Deleting a collection - Backend says Yes, Frontend says No. Can we fix that?

Hi all, Any user with the Custom/Manager role is allowed to create a new collection, but unless they also have the "manage all collections" sub-role, they won't be able to delete their own collections. This seems to be a limitation of the frontend only - calling DELETE on /api/organizations/<uuid>/collections/<uuid> (with the correct bearer token) works. But there is no button in the UI that allows a non-all manager to trigger it. There are two places in the web vault where collections should be able to get deleted • when visiting a collection (/#/vault?collectionId=<uuid>), there is a drop-down menu next to the collection title <img width="499" height="251" alt="image" src=" /> * the "delete" menu entry is simply missing • then displaying the list of all (top-level) collections (/#/vault?collectionId=all), after bulk-selecting collections <img width="1247"…