Is it technically feasible to separate the "creation" permission node for sign-based portals into (A) Standalone portals and (B) Obsidian portals?

I'd like to restrict essentially all Multiverse permissions from users, except:

1. The ability to convert old multiverse signs into 'new' ones,
2. The ability to create a new sign-based obsidian portal to any arbitrary destination.

The arbitrary destination availability pending permissions, of course. (E.g, users cannot sign-portal into worlds they are otherwise restricted from.)

For 1 this is already possible: multiverse.signportal.validate

For 2 I'll file this as a feature request (seperating the perms) and stage it for 2.2.

The arbitrary destination availability pending permissions, of course. (E.g, users cannot sign-portal into worlds they are otherwise restricted from.)

This is handled automatically by Core.

Doing some issue management. I will do this, but it's gonna take more time than I have tonight.

Pushing to 2.3.