Hi Ragnar, I just saw your question and tested it briefly. I created a new object (which created its version 1 and the source language automatically). I then released it. And then I deleted it successfully.

This corresponds to my memory of actually using Tridion Docs in production.

What definitely prevents you deleting an object is when other objects refer to it. Then you need to delete those first. For example going down the tree, deleting a publication, then its root map, then branch maps, then topics, then conref libraries and images. This is a precaution of course, to prevent deleting something that is used by something else that is still needed. Even if that need is just for an audit trail.

(Going down that tree of deletion can be a bit of a job if you have lots to delete, though of course that’s automatable via the API!)

Could you try creating a new topic, then releasing it, then deleting it?

I hope that I understand your question correctly, and also that I am not misleading you! Nevertheless my memory and my quick test do coincide on this point.

 Joe Pairman , I noticed in my 15.2 installation that a user has to have an Administrator role in order to delete objects in a released state. In fact, the "Delete" button in Organize Space is not visible for released objects unless the user has an Administrator role. I don't see anywhere in the UI or on the server where that functionality is configured, however. Is it hard coded in some way, or is it possible to configure it? Elizabeth Gschwind Ragnar Branæs 

Mark Novembrino , I think that privilege is still limited to Administrators. It’s not on the configurable list here: https://docs.rws.com/en-US/tridion-docs-main-documentation-1165616/user-privileges-986494

Of course it is a risky thing, deleting a released object. The idea of releasing, and the associated progress towards freezing a baseline / releasing an output, is to protect content from being deleted inadvertently. The limitation to admins mostly prevented such accidents. And I don’t think this came up as a suggestion when we made other actions configurable to non-admins, in the list linked above.

But if you had a strong reason for allowing some non-admin roles to delete released objects, it would be good if you could raise that in the Ideas section, and we could see if others would value that too.

Mark Novembrino , I think that privilege is still limited to Administrators. It’s not on the configurable list here: https://docs.rws.com/en-US/tridion-docs-main-documentation-1165616/user-privileges-986494

Of course it is a risky thing, deleting a released object. The idea of releasing, and the associated progress towards freezing a baseline / releasing an output, is to protect content from being deleted inadvertently. The limitation to admins mostly prevented such accidents. And I don’t think this came up as a suggestion when we made other actions configurable to non-admins, in the list linked above.

But if you had a strong reason for allowing some non-admin roles to delete released objects, it would be good if you could raise that in the Ideas section, and we could see if others would value that too.

Thanks, Joe Pairman . I don't have any reasons and agree with your caution about deleting released objects. Perhaps Ragnar Branæs  or Elizabeth Gschwind  have more input for their needs. I was just jumping in to help with the question.

To clarify, it's easy to delete a single new object. It's when references/links get involved that the challenge mounts.