[Feature]: Toggle between global and individual region management

[MeshMapperBot]

Platform: Other

Description:
The original idea behind the feature was for a bunch of fully interconnected city meshes, which is why it works the way it does today.

Watching how the app gets used worldwide compared to our local mesh has been genuinely interesting. There are a lot of use cases and thought processes out there that we didn’t originally design around. Looking back, I suspect some regions may have grouped too soon, or maybe our original framing was just flawed.

One idea I have been thinking about is adding an option in the multi-region admin panel: a toggle between ‘control all regions’ and ‘allow individual regions to do their own thing.’

Discord: https://discord.com/channels/1463383723327356992/1466576054670987294/1495235812344856676

Submitted by: mralders0n (Discord)

[n2aws]

In my opinion, I like the idea overall, but think the current suggestion is the wrong approach.

The problem currently is that the multi-region admins already have the power to make unilateral decisions for the individual/local regions. So, with that in mind.. putting the ability to "control all meshes" in the power of the multi-admin is just "more of the same problem", multi-admins have no incentive to allow local admins to manage their own regions.

Instead, I would say:

• Regions with no local admins, default to being managed by the multi
  • If the region gets a new local admin, have a toggle to opt-in/opt-out of muti-admin control
• Existing local regions get a toggle to opt-in or opt-out of multi-admin control.

This allows the local regional admin to decide if they want to manage the region independent of the multi, while still being a part of the multi for cohesive data collection and display.

As it stands right now, a multi-region admin can uniliaterally force local regions to use settings that aren't optimal for the local region. The only options a local admin has, is to "accept it" or "leave the multi"

I think the happy medium is, allow local admins (who are closer to the source, and better understand the local needs) of a region, to decide what the best fit is for them.

Taking this a step further, you could have it so that changes that a multi-admin makes, which are in conflict or change your local settings, would be highlighted. Thus notifying the local admin as to which local settings deviate from the multi-settings. (This would let them easily see at a glance what would immediately change, if they opt for multi-admin control.)

Expanding on that slightly, maybe implement a voting system? When multiple regions have opted-in to allow multi-admin.. When a multi-admin "suggests" a settings change (by changing it in their portal) each individual region gets to vote yes/no if they want the change implemented. If the majority say yes, the change takes affect. This removes the ability for a multi-admin to just unilaterally decide what settings apply to all regions, without coordinating with the local region admins. (This has been an issue in several multis. unilateral decisions without collaborating with local region admins.. Often, without the multi-region admin understanding fully how the change will impact the various regions under their control)