Assigning Ownership to Services

A service can be owned by one or more individual users and/or groups (either local accounts that have been set up in Commander or directory service accounts).

The three types of ownership that can be assigned to individual users and groups for a service are:

  • primary owner (one per service)
  • IT contact (one per service)
  • other (multiple "other" owners can be assigned to each service)

You can also assign a single organization to a service. This allows organization members to potentially view that service. (For information on what is required for an organization member to view a service, see For services to be visible to Service Portal users below).

In this topic:

When there are multiple service owners

A service can have multiple owners.

When the initial user or group is added to the service, it is automatically assigned a status of primary owner; any additional owners are automatically assigned as "other" owners. However, you can later change an owner's status to primary or IT contact (again, only one primary owner and IT contact are permitted).

Note that in the Service Portal, only the primary owner of a service can change the service's primary owner; the same holds true for the IT contact.

When multiple owners are assigned to a service:

  • responsibility for management can be delegated to multiple individuals, for example, help desk, IT contact, and primary owner
  • more than one user can access the service through the Service Portal
  • more than one owner can receive email notification about expiry
  • owners can receive email notification about policy alerts generated by vCommander

For services to be visible to Service Portal users

A user can be assigned an individual role, an organizational role, or both. The roles that are assigned to a Service Portal user affects whether the user can see the service:

  • Individual Service Portal role — If ownership of a service is assigned to a user with an individual Service Portal role, that service will be visible to the user when they are logged into the Service Portal with that individual role.
  • Organizational Service Portal role — If a service is assigned to an organization, the following conditions determine whether the user can see the service they when logged in as a member of that organization:
  • Service Portal Role To see the service
    • View Only
    • Customer
    • Delegated Admin

    By default, these roles aren't granted the permission of "Show All Organization Services".

    The service must be assigned to the organization

    and

    The user must be an owner of the service (primary, IT contact, or other)

    • Manager

    By default, this role is granted the permission of "Show All Organization Services".

    The service must be assigned to the organization

    or

    The user must be an owner of the service (primary, IT contact, or other)

  • Individual and Organizational Service Portal roles — A user can be an individual owner of a service and belongs to a group or organization that owns the service. In this case, the higher level of permissions is always used. For example, Jose is a member of the group Development, which is the primary owner of a particular VM, but Jose is also an "other" owner of the VM. In this case, Jose has primary owner permissions on that VM.

Automatically assigning service ownership

If a service is available for a Service Portal user to request, the user can automatically become its owner in the following situations:

  • When a user requests a service, that user is automatically assigned as primary owner of the deployed service.
  • When an organization member requests a service, the deployed service is automatically assigned to the organization, and the member is assigned as primary owner.

    Note that if the Primary Owner specified on the new service request form isn't the requester, the deployed service is still assigned to the requester's organization. Also note that to see this service, the primary owner must be a member of the requester's organization, or must have an individual Service Portal role. See Walk-through: Configuring Organizations to learn more about organizational roles and individual roles.

You can also assign service ownership through the following methods:

  • use the Default Ownership policy to automatically assign ownership to a new VM that's created outside the vCommander service request process, or directly in the managed system
  • configure a completion workflow with a Set Ownership step to configure ownership through a service request
  • assign an organization for an existing service through a change request

    Notes:

    • The ownership set for an existing virtual service, stack or auto scaling group automatically will apply to all of its children, overriding any existing ownership on child VMs. But you can add and remove non-primary owners to a child VM if required.

Manually assigning service ownership

In vCommander, you can select a single service and assign ownership for that service to an organization and/or one or more users or groups. See Assigning ownership for a service below.

If you want to assign ownership to many services, you can select an infrastructure element in vCommander 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. See Assigning ownership for multiple services below.

Assigning ownership for a service

Access through:

Views menu > Operational, Deployed, or Storage

Available to:

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

To assign ownership for a service:

  1. Go to a service in the tree or in a table.
    • For a VM, right-click and select Lifecycle Management > Set Ownership.
    • For all other service types, right-click and select Set Ownership.
  2. In the Set Ownership dialog, from Organization, select an organization.
  3. To assign individual owners, enter the login name or the email address of a user and click Add.

    The first owner you add is automatically assigned as primary owner.

    If you didn't select an organization in the previous step, when you assign ownership to one or more organization members, their organization is automatically selected. If users belong to multiple organizations, the first organization of the first user is added, but you can change the assigned organization before you saving the service ownership.

  4. To add more owners, enter additional login names or email addresses and click Add.
  5. (Optional) To assign an IT contact, select an owner in the list and click Assign IT Contact.
  6. (Optional) To assign a different a primary owner, select an owner in the list and click Assign Primary Owner.
  7. Click OK, when you have finished adding users or modifying their ownership assignments.

Assigning ownership for multiple services

Access through:

Views menu > Operational, Deployed, or Storage

Available to:

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

When you need to assign ownership to many services at the same time, you can assign ownership to the children of the following infrastructure elements:

  • Managed system
  • Datacenter
  • Compute cluster
  • Resource pool
  • Folder
  • Region
  • Virtual network
  • Azure Resource group
  • GCP project
  • GCP organization
  • GCP zone

To assign ownership to the children of an infrastructure element:

  1. In the tree, select an infrastructure element, for example a folder or resource pool, to display its Summary tab.
  2. In the Commands pane, click Set Ownership on Children.
  3. In the Set Ownership dialog, from Organization, select an organization.
  4. To assign individual owners, enter the login name or the email address of a user and click Add.

    The first owner you add is automatically assigned as primary owner.

    If you didn't select an organization in the previous step, when you assign ownership to one or more organization members, their organization is automatically selected. If users belong to multiple organizations, the first organization of the first user is added, but you can change the assigned organization before you saving the service ownership.

  5. To add more owners, enter additional login names or email addresses and click Add.

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

  6. To specify that new deployed 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.)

    Caution: Enabling this option automatically creates a Default Ownership policy targeting the selected infrastructure. To edit default ownership policies, see Managing Policies.

  7. (Optional) To assign an IT contact, select an owner in the list and click Assign IT Contact.

    Only one IT contact is permitted.

  8. (Optional) To assign a different a primary owner, select an owner in the list and click Assign Primary Owner

    Only one primary owner is permitted.

  9. Click OK, when you have finished adding users or modifying their ownership assignments.