> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/daas-guides/daas-administrators-guide/parallels-daas-interface/user-management.md).
# User Management
## Users and Administrators
There are three types of accounts in Parallels DaaS:
* Users: accounts that can be used to access the published resources using Parallels DaaS User Portal.
* Administrators: accounts that can be used to publish resources and add users in Parallels DaaS Management Portal.
* Owners: business owner accounts that must sign in via Parallels My Account. Have the same permissions as administrator accounts but can also manage Microsoft Azure subscriptions.
You can add users and administrators in the **Users** **Management** category.
### **How to add users and administrators**
To add a user or an administrator:
1. In the **Users Management** category, do one of the following:
* To add a user, select the **Users** subcategory.
* To add an administrator, select the **Administrators** subcategory.
2. Click the **New** button. A dialog will open.
3. On the left pane of the dialog, select the users or groups that you want to add. Selected users and groups will appear on the right pane, where you will be able to remove them from the selection.
4. Click **Add**.
### **How to remove users and administrators**
To remove a user or an administrator:
1. In the **Users Management** category, do one of the following:
* To remove a user, select the **Users** subcategory.
* To remove an administrator, select the **Administrators** subcategory.
2. Select the user or administrator you want to remove.
3. Click the three-dot menu (
) to the right of the **Display** drop-down menu and select **Remove**.
{% hint style="info" %}
Per browser instance, only one User or Administrator can be signed in.
{% endhint %}
## Workspace
### How to configure pool size
Pools are groups of virtual machines that are deployed and started before a user signs in, minimizing wait times for the user. In Parallels DaaS, all virtual machines belong to one pool. You can configure the maximum and minimum number of virtual machines available in the pool.
To configure the minimum and maximum number of virtual machines in the pool:
1. In the **Users Management** category, go to the **Workspace** subcategory.
2. In the **Minimum pool size** field, specify the number of virtual machines that must always be available in the pool.
3. In the **Maximum pool size** field, specify the maximum number of virtual machines that can be available in the pool at any given time.
Consider the following example:
If you set **Minimum pool size** to 5, 5 machines will be created and started before users sign in to the system. When the first user signs in, he gets access to the first machine from the pool, and a new one is added.
It is recommended to keep the pool size small to reduce costs, but big enough so that there are always enough virtual machines for new users.
### How to pause a pool
You can configure Parallels DaaS to pause a pool when its virtual machines are not in use, which can reduce costs.
When you pause a pool the following happens:
* Virtual machines that are not used for the specified period of time are deleted
* New virtual machines are not created automatically, even if there are fewer virtual machines than specified in the **Minimum pool size** field
A pool resumes normal functioning when a user requests an app or a desktop or an administrator starts editing the Golden Image.
To pause a pool:
1. In the **Users Management** category, go to the **Workspace** subcategory.
2. In the **Pause virtual machine pool** drop-down menu, select the time period after which the pool is paused.
### User Profiles
A user profile stores a user's personal desktop and application settings, along with other profile data used across sessions. In the **Profiles** subcategory, you can review profile sizes, find unusually large profiles, and remove profiles.
#### How to use user profiles
An FSLogix user profile is a collection of settings and application data associated with a specific user stored on a network location. It helps to minimize sign-in times and optimize file I/O between the host, client, and profile storage.
To enable FSLogix user profiles:
1. In the **Users Management** category, go to the **Workspace** subcategory.
2. Enable the **Store user profiles (FSLogix)** switch.
3. Do one of the following:
* If you have not created an Azure file share yet, follow the instructions in the [**How to create an Azure file share for FSLogix**](/landing/daas-guides/daas-administrators-guide/frequently-asked-questions/how-to-create-an-azure-file-share-for-fslogix.md) section to create one.
* If you already have an Azure file share, move to the next step.
4. In the **Share URL** field, specify the URL of the Azure file share.
5. In the **Storage account name** field, specify the name of your storage account.
6. In the **Storage access key** field, specify the access key of your storage account.
7. In the **Maximum profile size (GB)** field, specify the maximum size of a single user profile.
8. Restart all virtual machines.
#### How to view user profiles
To view user profiles:
1. In the **Users Management** category, select the **Profiles** subcategory.
2. Review the list of profiles. For each profile, the list shows the following:
* **Name**: The name of the user account.
* **Details**: The account that the profile belongs to, for example, `user@example.com`.
* **Size**: The size of the profile in GB.
* **Last Updated**: The date and time when the profile was last updated.
To find a specific profile, type in the **Search** field. To sort the list, click a column header.
#### How to remove user profiles
{% hint style="warning" %}
**Important**: Removing a user profile is irreversible. All files, documents, and settings stored in the profile are permanently deleted. You can't remove the profile of a user who is signed in.
{% endhint %}
To remove a single user profile:
1. In the **Users Management** category, select the **Profiles** subcategory.
2. Locate the profile you want to remove and make sure the user is signed out.
3. Click the three-dot menu () at the end of the profile row and select **Remove**.
4. In the **Remove Profile** dialog, click **Remove Profile** to confirm.
To remove several user profiles at once:
1. In the **Users Management** category, select the **Profiles** subcategory.
2. Select the checkboxes next to the profiles you want to remove and make sure the users are signed out.
3. Click **Actions** and select **Remove**.
4. Confirm the removal.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.parallels.com/landing/daas-guides/daas-administrators-guide/parallels-daas-interface/user-management.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.