Custom content without container


In my add-on I have content which is not directly associated with any space or page, it is global for the whole Confluence instance.

The documentation of the add-on descriptor states supportedContainerTypes must not be empty for any defined custom content. Also from tests I did with the REST API it is not possible to set no space when creating custom content.

So my question is:
Is there a way to create custom content which is not associated to any container?

And if not, is there any best practice to handle such a situation? One workaround I thought of would be to attach the custom content to the personal space of the add-on user. But this sounds rather hacky.

1 Like