Creates a new template group from an existing one or updates an existing template group's configuration. When the request body 'name' matches the 'templateGroup' query parameter, the endpoint updates the existing group. When they differ, a new template group is created using templates from the source group. QoS templates require a valid license.

Deployment behavior: There is no separate deploy/apply endpoint. Modifying a template group here or changing selections via POST /template/templateSelection automatically queues all associated appliances for orchestration. To determine which appliances are affected, call GET /template/applianceAssociation (no nePk) and find appliances whose templateIds include the modified group name.

Monitoring orchestration completion: After a POST, poll GET /template/history?nePk=<id>&latestOnly=true for each affected appliance. When the response includes a history entry for the modified template name with appliedOn timestamp newer than your POST time and status of 'successful', orchestration is complete for that appliance. If no new entry appears within your timeout, the appliance may still be pending or unreachable.

User Management template: The 'users' template contains a map of local appliance user accounts keyed by username. Each user has fields: self, enable, gid, password, gms_marked. Passwords are redacted (empty string) on GET; supply the new password in valObject on POST. Use GET /userAccount?nePk=<id> to verify user changes were applied to an appliance.

Related endpoints: Associate groups with appliances via POST /template/applianceAssociation. Check which groups an appliance has via GET /template/applianceAssociation?nePk=<id>.