If using IGC, the concept of monitor vs managed is no longer there. IGC will push if 'save & apply' is ever selected.
Added devices from 'new devices' will go into a folder/group based on Org string. If you're devices are pre-configured and going into a group that already has IGC enabled -> make sure that Auto-Config VC is disabled.
Best practices for a deployment that's moving from templates to IGC while still expanding:
Preconfigured APs:
a) Want to keep preconfigured settings? Then make sure Auto-config VC is disabled. May be a good idea to separate VCs based on their configs.
b) Want to overwrite preconfigured AP with group setting? Then make sure Auto-config VC is enabled. As soon as AP is added, after the 1st audit, IGC will push config to the AP and overwrite existing config.
New APs:
a) Want to adopt a specific group's config? Make sure that the group the IAP is about to be added in already has Auto-config VC enabled.
b) Want to start a new config from scratch? Make sure that the group the IAP is about to be added in already has Auto-config VC disabled. Alternatively, create new group -> add the new IAP to that new group -> then build config as desired.
Keep in mind that the folder the IAP is added into is based on the ORG string, so be aware of where the IAPs are going to be added when you add. You will see which folder / group the IAP will go into based on the confirm page when you try to add from new devices
Even through I had selected Folder: rob / Group: rob, it would try to redirect to the folder / group from the Org string