This is one of those unfortunate situations analogous to the problems caused by using PATs for things that we were never really adequately informed they weren’t intended for. In this case Organizations have been around for a good four or more years and have never really been introduced.
If they had been, and the management tool had not been so jealously tied in with a ‘partner’ tool, developers would probably have been keeping their misshapenpotato12345 format namespaces for their own private development purposes and creating additional organizations that they could assign meaningful namespaces to and also invite other users to access should the need arise, thus allowing them to also manage capabilities and preferences.
It is possible to add users to the ‘default user organisation’ which is normally associated with the random namespace, but I’ve never experimented with that and it doesn’t really seem appropriate.
I created an Organization for the first time in years yesterday. Using the Certification Console to do so is not as useful as It was when it was the SmartThings Console. It used to be that the name was a PascalCase version of the label and was folded to lower case as a namespace. Now both look like a long hash and are unusable.
Fortunately using the API directly still allows a useful name and so a corresponding namespace to be created. This namespace is much more useful for sharing purposes as it can not only be meaningful but it is owned by the Organization and not a specific User, which is a much less fragile arrangement.
Having the default User owned namespaces appearing in capabilities and preferences in shared device profiles and Edge drivers is utterly ridiculous. It should have been stomped on from day one. Indeed the whole idea of community sharing has never really been addressed adequately since the demise of the legacy platform. The community have been allowed to dig themselves into holes.
As ever I am taking this thread too far off topic …