Correct, Think of the global app list as just a list of apps you want to "monitor" the version numbers of. Then at the client is where you actually approve a package. The approved packages at this level cover all agents "Enabled" under the client.
As for the process, your pretty close.
1 Add and Enable to the global apps list all apps you want to allow across MSP
2 (if using choco proxy) add proxy source to global source lists - optional
3 (if using Chocolatey Licenses) add license text to global license configuration. - optional
4 (if using Network Cache) Edit each location console under client, Add network info along with user and password to network drive EDFs -optional
5 Open C4A in Client console, enable workstations and / or servers
6 Once Agent list appears, If using either sources or network cache, select one agent at the location you want to enable network cache, right click and open menu and select "Set Location To Use UNC cache" or "Set Client to Use Sources" if you are using either Network cache or Sources like a Chocolatey proxy or other repos. - optional
7 (If using a Chocolatey License) select agent, right click menu and select to "Push out Chocolatey License" - optional
8 Select Approve Apps button, approve one or more software titles for the client. -optional
9 Select the Set Schedule button, defaults to daily updates. Select to reschedule to weekly or monthly if needed. -optional
10 (if using Network Cache) select an agent for each location using network caches. Select 1 agent at location and right click menu to select to "Set Agent As Cache Manager". This forces this agent to populate the cache and maintain it. -optional
At this point you could stop and the plugin should take over and start managing agents. You have the option to manually force agents to proceed but you would need to do it in the correct order to not receive bad data or errors.
Example: Running an agent scan when the Chocolatey framework has not yet been deployed to agents would cause a script error and no data from agent.
Each agent has a set of EDFs under "Chocolatey" that set the state of the agent and also records it's progress. You can use the EDFs to trigger certain actions.
Example: You deployed a source but decided it was bad so you updated the source and want the agents to reprocess the sources. By editing the agents EDF, unchecking the Sources Enabled checkbox and making sure the Enable Sources checkbox is checked, the agent will rejoin the deploy sources group and then redeploy new sources you configured.
It may take a little time for an agent to walk its way through each step (sub group) to get to installing and updating packages which is the final steps for a successfully managed agent.
Also I can not stress enough to make sure you always add and approve Chocolatey itself and it's dependencies.
Visit this post for more on why we add these and what actually to add.
viewtopic.php?t=6319
When you go to post an issue with a deployment or such make sure to include a screenshot of all your EDF settings for the agent in question. Include what groups you currently see agent in. Any script and or command logs the agent may be generating during any given phase of the process.
I hope this helps!