Assigning Ownership to Services

About service ownership

Who can own a service?

A service can be owned by one or more individuals and groups. A service can also be assigned to an organization. (Note that a service can be assigned to only a single organization.)

You can assign either local accounts that have been set up in Embotics® vCommander® or directory service accounts as owners. Both individual and group owners can be assigned.

What are the benefits of organizational ownership?

Because an organization can have one or more managers, with permissions to manage an organization's VMs, organizational ownership allows you to delegate administrative tasks. Organizational ownership also allows configuration of resource- and cost-based quotas for your consumer groups.

What are the types of ownership?

There are three types of individual and group ownership:

primary owner (one per service)

IT contact (one per service)

other (multiple "other" owners can be assigned to each service)

Note that these ownership types do not apply to organizations; they apply only to individuals and groups.

The first account added to the service is automatically assigned a status of primary owner. If a primary owner has already been assigned, any additional owners are automatically assigned as "other" owners. Note that only the primary owner of a service can change the service's primary owner; the same holds true for the IT contact.

Why assign multiple owners?

When you assign multiple owners 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

What ownership type takes precedence?

If a user belongs to a group or organization that owns a service, and the user is also an individual owner of a service, 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.

How do I ensure that a service is visible to an organization member?

For a service to be visible to an organization member:

The service must be assigned to the organization

and

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

How do I ensure that a service is visible to an organization manager?

When you assign the Organization Manager role to a user, that user is granted the permission "View All Organization Services." Therefore, for a service to be visible to an organization manager:

The service must be assigned to the organization

or

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

How can I set ownership automatically?

When any 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.

NotePencil-smallIf the Primary Owner specified on the new service request form is not the requester, the deployed service is still assigned to the requester's organization. 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:

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 for a requested VM

assign an organization for an existing VM through a change request

Note for virtual services and stacks
NotePencil-smallOwnership set for an existing virtual service, stack or auto scaling group automatically applies 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.

Assigning service ownership

Access through:

Views menu > Operational, VMs and Templates, or Datastore

Available to:

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

To set ownership for a service:

1.Right-click a service in the tree or in a table.

2.For a VM, right-click and choose Lifecycle Management > Set Ownership.

For all other service types, right-click and choose Set Ownership.

3.In the Set Ownership dialog, select an organization from the Assign to Organization drop-down menu.

NotePencil-smallIf you assign ownership to one or more organization members in the next step and no organization was previously assigned, their organization is automatically selected.

4.To assign individual owners, enter the login name or the email address of a user and click Add. The first individual owner you add is automatically assigned as primary owner.

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

6.You can assign an IT contact or primary owner by selecting an owner in the list and clicking Assign IT Contact or Assign Primary Owner.

Assigning ownership for many VMs

Access through:

Views menu > Operational, VMs and Templates, or Datastore

Available to:

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

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, select an organization from the Assign to Organization drop-down menu.

NotePencil-smallIf you are assigning ownership to one or more organization members, in order for the organization members to have access to the services, you must also assign ownership to their organization.

4.Enter the login account name or the email address of the user for the account you are adding and click Add.

5.Repeat the previous two steps to add more user accounts as owners.

6.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.

7.To specify that new deployed VMs in this level of the tree should have the same ownership, enable Automatically set ownership on new VMs. (You can enable this option only if you have the Superuser or Enterprise Administrator role and Administrator access rights.)

caution

Enabling this option automatically creates a Default Ownership policy targeting the selected infrastructure.