Thanks for taking the time to reply, offering your insights and explanations, and offering to take this suggestion as an RFE!  Truly outstanding customer service.

As a former professional dev, I completely agree with the reasoning behind the way things are done.  But I think I'm probably not alone in finding myself in the position I described, and quite often.  If the customer IS interested in assuming ownership/management of their network (which of course is what I recommend), your app makes it downright trivial to do so.  But in my experience, unfortunately it's all too common that my customers feel that they hired ME to worry about all of this networking stuff, and once I have it set up and operational, they don't want any part of it.  You and I might cringe at that attitude, but there it is.  So for those customers, if they don't want to be bothered doing something as simple as setting up an online account so that I can transfer ownership to them, so be it... that's on THEM.  And if, down the road, they find that they DO need to make a change and find that they have to recreate the whole network from scratch... well, they'll reap what they sow.  But I think it still feeds a need to have some method (even if it's advanced and secret and you need five signatures to use it) to remove the network from the app without tearing down the network -- essentially "abandoing it from management" -- with full knowledge of the consequences of doing so.

So carrying this forward for me as an RFE is greatly appreciated.