I just watched the Sage U intro videos, and one detail jumped out at me: the login used is a Sage ID, with nothing about linking the "Sage Connect Account" to a customer license.
So, as a Sage Partner, I don't think it's right for me to do the setup for a client under my Sage ID... and if we use a customer's Sage ID, what about job changes (i.e. that user leaving the company)? Would we need to take down the site and reconfigure it to run under someone else's credentials? (In the FAQ, linked below, taking the site down basically erases all site history, and expires all links).
Will multiple users (each with their own Sage ID) be able to manage / work with the SC site data?
Will we need to get the customer to get us connected using their Sage ID (with 2FA), if want need our assistance with any kind of troubleshooting / settings...?
Is there a way to set up different Sage ID permissions for the potentially multiple company codes on a client's Sage 100 installation?
At this point it looks like this new feature is still at the "wow, isn't this cool!" stage, with many critical details yet to be worked through... but of course I could be wrong.
From the FAQ:
Indeed... not a mature product yet.

What about upgrades / server changes? Will that break all the existing links?

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------