Assigning Ownership

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

  • Primary owner (one per service) — If you're the primary owner of a service, you can:
    • Add another owner to a service.
    • Remove yourself as the primary owner of a service without assigning another primary owner (you remain as an owner).
    • Assign another primary owner to a service where you remain as an owner.
    • Remove all owners of a service with the exception of the IT contact.
    • Remove yourself completely from owning of a service. Any association between your user account and the service is removed and your account name is removed from the list, and the service is removed from your tree in the Service Portal.
  • IT contact (one per service) — If you're the IT contact for a service, you can unassign yourself as the IT contact.
  • Other (multiple "other" owners can be assigned to each service) — If you're an owner other than the primary owner or IT contact for the service, you can't change ownership information.

When you request a service, you're automatically assigned as primary owner of the deployed service.

When you request a service as an organization member, the deployed service is automatically assigned to your organization, and you're assigned as primary owner.

To change ownership for a service:

  1. From Applications, select the service for which you want to change ownership information.
  2. From the Actions menu, select Attributes > Set Ownership.
  3. In the Set Ownership dialog, you can do the following:
    • To add a new owner, enter the username or the email address of the user for the account you're adding, and click .
    • To change the ownership for a user, from the Type drop-down icon for the user, select an ownership type.
  4. Click Save when you have finished adding users or modifying their ownership assignments.

Note: The ownership set for an existing virtual service, application stack, or auto scaling group will automatically 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.