Seperate space permissions for adding and removing rooms

Your use case

First of all, thanks for your work! Sorry if this should go somewhere else. Please tell me in this case and I'll move and link it.

What would you like to do?

I'd like to allow all space members to add rooms by default, but not to remove any rooms they didn't create. Basically as it's already possible outside any space (let me call this "top level" for now) by default.

Why would you like to do it?

Our group has a subspace in an organization-wide Matrix instance and it would be nice to keep the group-related rooms within that space such that the corresponding admins have power over it. Otherwise, if the last room admin left the group, we'd have to annoy the instance admins to give us permissions.

How would you like to achieve it?

Would be nice to have separate space permissions to add rooms and delete/manage rooms such that one could easily manage those in a client.

Have you considered any alternatives?

• The current workaround is to give all space members permissions to manage rooms by default. That also allows them, however, to remove e.g. our main staff chat, which is undesired.
• Create another subspace in our group space where they have the "manage rooms" permission. However, that would be a bit dirty and confusing in my opinion (feel free to prove me different^^).
• Let them create their rooms outside of our group space. Then the group admins don't have control over it anymore, which defies parts of the idea of this space.

[backreference: previously posted as Element Web issue]

Start with this issue and its backreference to the previously posted Element Web issue. Review how Matrix currently represents top-level and space room-management permissions, then define separate permissions for adding rooms and removing or managing them. Done means the specification clearly describes the distinct permissions and their intended behavior.