Assigning Service Ownership with the Default Ownership Policy

Use the Default Ownership policy to automatically assign ownership to new services, ensuring that you can track who's incurring service costs. This policy works in three ways:

  • During a vCommander deployment (automated or manual), if vCommander finds a policy targeting the selected destination, it calculates the policy actions and combines them with the other metadata (inherited from the source template and supplied on the request form). During automated deployment, vCommander applies the combined values. During manual deployment, vCommander populates the wizard with the combined values.
  • The policy is triggered when a new service is created directly in the managed system that is, outside of vCommander.
  • The policy is used to assign ownership to costs in public cloud billing data for the purposes of Cost Analytics.

This policy reduces the time required to set service ownership and ensures that services are always assigned to an owner who can manage them, and are always visible to organization members.

You can also set ownership information with a workflow step. To ensure that the proper values are set, it's best practice to set metadata through policy or through a completion workflow, not both. The metadata values that are applied last are those that take effect.

See also Assigning Ownership to Services.

How the Default Ownership policy affects templates

The Default Ownership policy changes ownership of templates, but policy actions aren't performed for templates.

Configuring the Default Ownership Policy

Access through:

Configuration menu > Policies

Available to:

vCommander Role of Superuser and Enterprise Admin

Administrator Access Rights

  1. On the Policies tab, click Add.
  2. On the Choose a Policy page, select Default Ownership from the list of policies, then click Next.
  3. On the Policy Name/Description page, enter a name, for example, "Default Ownership Policy for Windows in Production", and an optional description, then click Next.
  4. On the Choose a Target page, from the Target View Type list, choose Operational or Deployed.

    If a VM is deployed into a location where multiple policies target the Operational view and the Deployed view, the policy targeting the Operational view takes precedence.

  5. To select the target for the policy, navigate to the appropriate infrastructure elements in the Operational or Deployed tree on the right, then click Next.

    Any configuration of this policy on a system-wide basis can affect all managed systems that are managed by vCommander now and can affect all managed systems that are added to vCommander in the future. If you don't want all managed systems to be automatically affected by this policy, don't select Operational or Deployed as a target but rather select a managed system or any infrastructure elements within a managed system.

  6. On the Configure the Policy page, select Enable Policy for the policy to come into effect immediately after you finish configuring it.
  7. From the Take Action drop-down, select from the options:
    • Notify Only: If the policy is triggered, no action is taken for the service. An alert is created, notifying you that the policy has triggered. See also Subscribing to Policy Alerts.
    • Run [Workflow]: Existing command workflows appear for selection, organized by target type. If the policy is triggered, the selected workflow is run.


      • You must choose a workflow with a target type that matches the target of the policy; otherwise, the workflow will fail. For example, if the selected workflow's target type is "VM", the workflow will fail if the policy targets a database. A workflow with a target type of All Types can be run on all service types.
      • Click Add Workflow to set up a new command workflow.
  8. In the Default Owners area, do the following:
    • Choose an organization to make new services visible to users in an organization.

      If you assign ownership to one or more organization members in the next step, their organization is automatically selected. For a service to be visible to an organization member, the service must be assigned to the organization.

    • To assign users to the new service, in the Login/Email field, type a login ID or email address, then click Add. Any account you add must be a local user or group account set up within vCommander or a directory services user or group account.
      You can add more than one account and you can assign a primary owner and an IT contact. The first owner added to the policy is automatically assigned as a primary owner; you can change that assignment and the IT contact assignment as required.
  9. If you want to allow children of the targets to have their own instance of the policy, enable the last checkbox.

    Enabling this option allows other instances of this policy to be applied to any infrastructure elements and services that are children of the parent infrastructure element you have selected (an override). See Walk-through: Configuring Organizations for an example of how this override can be useful.

  10. On the Summary page, review the settings and click Finish.