# Managing user accounts > Adding users for any of the services in your organization is done from the Admin section. You cannot add users to a service from the service itself. Adding users for any of the services in your organization is done from the Admin section. You cannot add users to a service from the service itself. :::note Changing a user email address is not supported. If a user email address needs to change (for example, due to a company domain change), invite the user using their new email address, then delete the account associated with the old address. ::: ## Adding accounts ### Adding user accounts 1. Go to **Admin** >organization > **Accounts & local groups** and select the **User accounts** tab. 2. Select **Add user**. The **Add user** panel opens from the right of the window. 3. Fill in the fields with the user's details. * If you are integrated with an external directory, the password is not required and, if system email notifications are set up, the user receives an email with their account details and can set their own password at first login. * If not, you must set a password for the account. The user will need the email address (or username) and password to log in. 4. Under **Group membership**, select the checkboxes for the groups to which you want to add the user. If your groups are properly set up, the user should already have the access they need to start working in Private Test Cloud. 5. Select **Save** to add the account. The panel closes and the new account is available in the list of user accounts. ### Adding robot accounts 1. Go to **Admin** >organization > **Accounts & local groups** and select the **Robot accounts** tab. 2. In the top right, select **Add robot account**. The **Add robot account** panel opens at the right of the page. 3. In the **Name** field, type a descriptive name for the account. :::important Choose wisely. You cannot change the name of the robot account later. If you need to rename it, you must delete the account and create a new one with a new name. ::: 4. Optionally, under **Group membership**, select the checkbox for groups to which you want to add the account. Adding the account to one or more groups means it inherits any roles, user licenses, or robot settings defined for the group. 5. Select **Add**. A success message appears at the top of the panel and further guidance is displayed. The robot account is added and is now visible on the **Robot accounts** page. It is also added to the groups you selected. Continue the setup of the robot account in UiPath® Orchestrator as you would set up a user account for unattended use: [Unattended Setup](https://docs.uipath.com/orchestrator/v2022.10/docs/managing-robots-modern-folders#unattended-setup) . ## User group considerations ### Leveraging groups By leveraging user groups you can grant default access to all group members without the need to set the access level for each user individually. By granting roles and permissions to groups in your services and adding users to the desired groups in Cloud Portal (be it when inviting them, or by editing them afterward), all group members inherit that access level with no further configuration required You just need to ensure the groups are referenced in the services you use. * Default user groups (i.e. groups provided by UiPath®) are automatically referenced in newly created services, and they are configured with a set of default permissions. You can change this default configuration at any moment if you choose so. * For services created before the User Groups feature was launched, default user groups are not referenced. They must be added manually. * Custom user groups (i.e. your own custom groups) must be added manually to your services irrespective of when they have been created. The following table describes where you can learn about adding user groups for each service: Service Learn Orchestrator Adding user groups at the tenant level in Orchestrator services. Adding user groups to folders in Orchestrator services. ### Not leveraging groups If you do not want to use groups, leave any user to the default **Everyone** group, which comes with no roles attached by default. This implies access control is performed on a per-user basis; users must be granted roles individually in each service. The following tables describes where you can learn more about granting access rights to users: Service Learn Orchestrator Granting access-rights to users at the tenant level in Orchestrator services. Granting access-rights to users at the folder level in Orchestrator services. ## Removing users To remove a user, select the corresponding **Delete** button in the **Users** page, and then **Delete** to confirm. Alternatively, select one or multiple users, and select the **Delete** button. The deleted user/users are no longer displayed on the **Users** page and they cannot access your organization. :::note * When you invite someone to join your organization, a new user account is created. Should you remove this user from your organization, they can log in independently by creating a new organization. While they can't access your organization's data post-removal, they may still use their account in a new organization. * You cannot delete your own user. Ask another organization administrator to perform the changes for you. ::: ## Creating custom user groups 1. In the **Accounts & local groups** page, go to the **Local groups** tab. 2. Select **Add local group**. The **Add group** window is displayed. 3. Fill in the **Name** field. 4. On the **Names** field, add users to the group. Only users that have been invited to your organization beforehand are listed. Unlike default user groups, custom groups need to be added manually to your services to ensure the correct mapping between the group membership and the corresponding roles in those services.