Provide Deployment Access to Additional Users
- Last UpdatedAug 01, 2024
- 2 minute read
When you install deployment server, additional security roles will be created. By default the local Windows user groups are associated with the security roles as members. These members control access to the deployment server's functionality. You can add additional users to the roles using Configurator (see Modify the Members of a Security Role).
Note: If your Deployment Server is on a separate computer to the System Management Server, you need to run your IT infrastructure as a domain. To allow authorization in this type of distributed system, only add domain groups to a deployment security role. Avoid adding individual users to these roles.
The security roles and local Windows user groups will be created and mapped as following:
|
Security Roles |
Windows User Group |
Description |
|---|---|---|
|
Deployment Administrators |
SCADA.DeploymentAdmins |
Members of this role can add or remove client computers to/from deployment server. They can also perform upload and deploy operations. |
|
Deployment Uploaders |
SCADA.DeploymentUploaders |
Members of this role can upload a new project version to the deployment server. |
|
Deployment Users |
SCADA.DeploymentUsers |
Members of this role can deploy a new project to a connected deployment client computer. |
When the deployment server is installed, the user that is logged in to the computer is automatically added to each of these groups.
For example, you may have a number of engineers that need to add project versions to the deployment server. To enable this, each engineer's Windows user account needs to be added directly or via a domain group to the "Deployment Uploaders" security role locally on the deployment server.
Refer to the documentation provided by Microsoft® to determine how to add user accounts and domain groups to a Windows™ user group.