Set Resource Ownership

In the Admin Portal, you can select a single resource or virtual service and set the ownership for that resource or virtual service to an organization or to one or more users or groups.

The ownership that's set for AWS stacks, GCP deployments, or Azure Resource Groups is also set for all of the resources that are part of that parent resource.

Also, if you want to assign ownership to many resources or virtual services, you can select an infrastructure element in Commander and assign ownership for all of its child elements. The ownership of the child elements can be assigned to an organization and/or one or more users or groups.

Set ownership for resources

Access:

Views > Inventory > Infrastructure, Applications, or Storage

Available to:

Administrator and All Operator Levels of Access Rights (except where noted)

  1. Select a resource or virtual service in the Inventory tree or in a table.
    • For a VM, double-click the VM, then select Actions > Lifecycle Management > Set Ownership.
    • For all other resources or virtual services, double-click the resource or virtual service, then select Actions > Set Ownership.

      For Kubernetes resources, the Applications view allows you to select a namespace and see all of its child resources that the ownership will be applied to. For all views, the deployed namespaces are also listed on the Namespaces tab; from this list you can select multiple namespaces and set the ownership for them.

  2. In the Set Ownership dialog, do any of the following:
    • Add an organization — From Organization, select a listed organization.
    • Assign individual owners — From Add Owners, enter the username or email address of a user and click Add.

      You can add multiple owners; the first owner you add is automatically set as primary owner.

      If you didn't already select an organization, when you set ownership to an organization member, their organization is automatically selected. If the assigned users belong to multiple organizations, the first organization of the first user is selected, but you can change this assignment.

  3. Optional: To set an IT contact, select an owner in the list and click Assign IT Contact.
  4. Optional: To change the primary owner, select an owner in the list and click Assign Primary Owner.
  5. Click OK.

Set ownership for child resources

You can select an infrastructure element in Commander and set ownership for all of its child resources or virtual services. The ownership of the child resources or virtual services can be set to an organization and/or one or more users or groups.

You can set ownership for the children of the following infrastructure elements:

  • Cloud account
  • Kubernetes cluster
  • Datacenter
  • Compute cluster
  • Resource pool
  • Folder
  • Region
  • Virtual network
  • GCP project
  • GCP organization
  • GCP zone

When you set the ownership for the children of a managed Kubernetes cluster, ownership is only set for its deployed child resources (that is, those displayed under the Applications tree). In addition, the cluster's three standard namespaces, "default", "kube-public", and "kube-system" are excluded. You must manually set ownership for each namespace individually.

Access:

Views > Inventory > Infrastructure, Applications, or Storage

Available to:

Administrator and All Operator Levels of Access Rights

  1. Select an infrastructure element in the Inventory tree, select Actions > Set Ownership on Children.
  2. Optional: In the Set Ownership dialog, select an Organization.
  3. To set individual owners, enter the username or the email address of a user and click Add.

    If you're setting ownership for organization members, you must also assign ownership to their organization for those members to have access to the services.

  4. To add more owners, enter additional usernames or email addresses and click Add.

    By default, added owners are appended to the current list of owners. If you want to replace the existing owners, enable Replace existing owners.

  5. To specify that new deployed resources or virtual services in this level of the tree should have the same ownership, enable Automatically set ownership on new resources.

    To enable this option, you must have a Superuser or Enterprise Admin role and Administrator access rights.

    When this option is enabled, a Default Ownership policy is automatically created that will target the selected infrastructure. To edit Default Ownership policies, see Manage Policies.

  6. Optional: To assign an IT contact, select an owner in the list and click Assign IT Contact.
  7. Optional: To assign a primary owner, select an owner in the list and click Assign Primary Owner.
  8. Click OK.

Related topics