FortiClient Cloud Distribution and Updates

[Fishmonger]

I'm confused how updates work for Forticlient, in order to upgrade the client I've read that I need to use the 'Deployment and Installers->Forticlient Installer' and 'Manage Deployment', the strange thing is it forces me to attach an invite when creating the forticlient installer.

I've already added devices using 'Endpoints->Invites'.  I added my own email in the invite section, and now it seems to be deploying them all, but why did I need to add myself as an invite to accomplish this when I'm deploying to 10+ devices I've already added?

Theres also an option 'Reboot When Needed' which is confusing.  I want it to install but to not auto-reboot, so am I disabling Reboot when needed; except if I do enable it there's an option to Notify User to let them decide, but that is only supported on older versions of Forticlient.  I'm at a loss as to what to do, I'd like a notification, but if its on a newer version of Forticlient does it then auto-reboot?

[MZBZ]

That is by design. An installer needs to be bound to an invite. Installers created on EMS will try connecting to that EMS by default. The deployment mechanism first uninstalls the current installed FortiClient and then installs the one you have selected in the deployment package which will autoconnecto to EMS with that invitation. You may use group assignment rules to assign endpoints registering with a specific invitation code to a group and assign policies to that group...

[Fishmonger]

So if I want to send one single invite that connects to EMS automatically how would I go about doing so?   Presumably it would be the Forticlient Installer section, which is required to connect to EMS, but how do I avoid sending multiple emails when I have to create an initial invite first?