Legacy Deployment Permissions

Legacy deploymentDeployment permissions determine the access level that users have on legacy deployments and also the access level that users have on all Data Collectors provisioned with the deployment.

Note: Legacy deployments are included with legacy Kubernetes integration which is enabled only for some paid accounts.

When provisioned Data Collectors are registered with Control Hub, they inherit the same permissions assigned to the legacy deployment. For example, if you grant a user Execute permission on a legacy deployment, that user also has Execute permission on all Data Collectors provisioned by that deployment.

After provisioned Data Collectors are registered, users with the Organization Administrator role can modify the permissions on any provisioned Data Collector from the engine details page just as they can on any manually administered Data Collector. As a result, Data Collectors provisioned by the same deployment can be granted different permissions.

When you share a legacy deployment, you can grant users and groups the following access levels to the deployment and to Data Collectors provisioned with the deployment:

Read - View the details of the legacy deployment and of all Data Collectors provisioned with the legacy deployment.
Write - Edit and delete the legacy deployment. Assign labels to all Data Collectors provisioned with the legacy deployment.
Execute - Scale, start, and stop the legacy deployment. Start jobs on all Data Collectors provisioned with the legacy deployment - also requires execute access on the job and read access on the pipeline.