So, first off, the software should be installed using an Administrator account or a user with Admin rights. However, after the installation, FreeFlow Core mostly does not need users to access the windows desktop. As such, you will be using the "FreeFlow Core" users which you can set an administrator and then specific user accounts in the FreeFlow Core software (web browser).
Then for the Windows server / computer if a user needs to access the computer, it is possible to add standard users to windows that can of course then access and use FreeFlow Core. They would of course be blocked from doing some things like maybe creating shared network folders etc based on the user credentials. But they can access the FreeFlow Core software via a browser. Then when needed, log on via the admin account to do things like Windows OS updates, create network shares, activate FreeFlow Core licenses or update FreeFlow Core software (should always be done with admin account).
I would not recommend running any of the FreeFlow Core services on only a 'user' account. Some modules will fail to run due to insufficient access rights. Often the specific module licenses will not activate.
I have many customers where IT sets up the server OS using their admin accounts, install Core, then we validate the software is running and working, setup an admin and users in the FreeFlow Core software, and then pass it over to the users. At that point, none of the users have access to the windows server. When needed, we contact IT, run the necessary updates and move on. Thus the users dont need admin rights (but it is much easier when someone in production has the admin rights when needed).
Hope this helps
