Name
Name for the Agent Group. It is recommended to give some descriptive name such as CloudProd or OnPremProd. Every Agent group needs to have unique name, even between Environments.
Shared State Store
Activate this if you want to use an external database for the Agent Store. This is a standard SQL Server connection string. The installation is easiest with Integrated Security, but you can use a dblogin and provide the username/password for the login. If you use separate username/password credentials you will need to run the database initializer separately when installing the Agent, unless the connection string that is used has DB admin privileges. If the connection string has admin privileges, then the Agent will have DB Admin privileges.
Allow running test process
If this setting is on, it allows a Task test to be run in the Agent Group.
Log process executions to blobs
If this setting it on, individual step executions will be logged to blob storage or file systems instead of the database. This allows you to log and retain much more data without exhausting the database.
Cross-Platform
If this setting is on, the Agents in this Agent Group can be installed on Windows and Linux machines. It can only run Processes that target NET Standard 2.0 or .NET 6.0.
Allow new Agents to connect to Agent Group
If this setting it on, any Agent that reports a valid heartbeat will have a Cloud Agent generated for it. This is useful if you have dynamically scalable Agent instances in a Kubernetes cluster, for instance.
Please note that all of these settings are stored in clear text in the Agent installer. If you are not comfortable with storing credentials in the Frends UI you can omit them and then add them locally when installing the Agent.