Move Existing Users into Organizations

This topic provides more information if you've upgraded and want to begin using organizations. There are special considerations when moving existing users into organizations.

See also the following articles:

Create an organization for existing users


Configuration > Identity and Access > Organizations Tab

Available to:

Commander Roles of Superuser and Enterprise Admin

To create an organization and move existing users into it:

  1. On the Organizations tab, click Add.
  2. On the Name and Members page, provide a name (for example, "Development").
  3. To add users from a list of users and groups that have already been added to Commander, click Add Existing User.
  4. In the Add Existing User dialog, select one or more users and groups.

    The user's existing role is pre-selected in the Portal Role menu. Optionally, assign the user a different Service Portal role.

  5. Optional: Select Primary contact of this organization. Selecting this checkbox means that you can configure workflows to automatically send emails to this member.
  6. The most common reason for emailing the organization manager is for service request approval. It can be useful to assign multiple primary contacts for each organization, so that multiple individuals automatically receive approval emails. For more information, see Configure a Quota-Based Service Request Approval Process.

  7. Click Add.
  8. If the user or group you added is an owner of one or more VMs, the Add User To Organization dialog will prompt you to decide what action you want to take for the user's service ownership:

    Keep in mind that you can always reassign service ownership later. For more information, see Set Resource Ownership.

    • Move the user's account and services into the organization (recommended) — If you select this action, the user's services become visible to the organization, and the user's role outside the organization is deleted. This choice results in a simpler user experience, because the user logs into the Service Portal with an organizational role. (Note that only those VMs on parts of the virtual infrastructure that you have access rights to are moved. For more information, see Assign Access Rights to Administrative Users.)
    • Add the user to the organization but leave the services assigned to the user's individual account — If you select this action, the user's services don't become visible to the organization, and the user's role outside the organization is retained. This choice is recommended only if the user's VMs are personal, and shouldn't become visible to the organization. The user will now have both an organizational role and an individual role and will need to switch between these views in the Service Portal. For more information, see Multiple Roles and Membership in Organizations.
  9. When you've finished adding users, click Next.
  10. On the Organization Properties page, you can optionally associate key pair credentials with the organization and select the Service Portal landing page.
    1. By default, a key pair is required to open a secure SSH connection to Amazon EC2 Linux and Solaris instances. See Enable Key Pair SSH Connections to Amazon EC2 VMs to learn how to set this up. To associate key pair credentials with this user account, do one of the following:
      • To use existing key pair credentials, select one from the Key Pair Credentials list.
      • To add a new set of credentials, click Add Credentials.
    2. Select the Landing Page for this organization, keeping in mind that users will need the appropriate permissions to view the page you select. Options for the landing page are Dashboard, Cost Dashboard, Service Catalog and External Page. For more information on setting user permissions, see Customize Service Portal Roles for Users. For more information on external web pages, see Provide access to external web pages.
  11. Click Next.
  12. Optional: On the Custom Attributes page, you can set values for existing custom attributes for the organization.

    For more information, see Work with Custom Attributes.

  13. Click Next.
  14. Optional: On the Quotas page, you can set quotas for the organization. When configuring cost quotas, select the currency to be used for cost quotas.

    For more information, see Set Organization Quotas.

  15. If you've set a quota for the organization, on the Member Quotas page, you can also optionally set quotas for individual organization members.

    For information on setting quotas for organizations and specific members, see Set Organization Quotas.

  16. Click Finish.

To learn how to modify existing organizations, see Create Organizations.