Why does removing scopes or the Connect remote require admin approval?

[AdamAhmed]

I’m looking at Minor version updates (Connect to Forge)

It says that removing the Connect remote requires admin approval after the initial switch. Why?

Similarly, removing any scope after the initial switch requires admin approval. Why?

Those seem like they would be perfectly benign actions. Right now, I am seeing that I will have to get everything done in one go, if I understand correctly? I can’t release and iterate and refine my scopes and remove my Connect remote later.

[SimonPilkington]

Thanks @AdamAhmed, looking at that documentation it is misleading/inaccurate in parts and I have been able to update it.

As the updated page now states, neither removing the Connect remote nor removing scopes require admin approval but do require a developer-initiated bulk upgrade. This command can be initiated via the Forge CLI and will update all app installations from a selected version to any eligible higher version without requiring admin approval.

The bulk upgrades feature is designed to support exactly what you mentioned - the ability to iterate and refine scopes post migration to Forge and then the removal of the Connect remote in order to get to a fully Forge app without requiring admin approval.

Thanks for pointing this out and let me know if you have any further questions.