> 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/pd-ag/getting-started/dividing-users-into-groups.md).

# Dividing Users into Groups

In large organizations with multiple Macs, there may be groups of Parallels Desktop users with very different needs in terms of capabilities and restrictions, from a software engineer who develops for multiple platforms and needs a dozen virtual machines to test every possible scenario to a back-office staff who would benefit the most from [Single Application Mode](/landing/pd-ag/provisioning-and-activation-of-parallels-desktop/alternative-deployment-methods/alternative-mass-deployment-via-deployment-package/preparing-the-autodeploy-package/single-application-mode.md).

{% hint style="info" %}
**Note**: From a system administrator's point of view, dividing the user base into groups is useful for applying specific policies and/or provisioning tailored [Golden Images](/landing/pd-ag/preparing-virtual-machines-for-deployment-and-securing-them/golden-images.md).
{% endhint %}

The best way to maintain flexible arrangements is by dividing users into groups, each of which would require a sublicense. We recommend that you create an organizational chart to plan your groups beforehand.

As an organization, you can choose what type of license activation you want to use: a per-device one where you activate each individual installation with a product key, a per-user one that requires [signing in with SSO](/landing/pd-ag/parallels-desktop-for-mac-enterprise-edition-features/activating-using-a-corporate-account.md), or a mix of the two, which Enterprise Edition also allows.

To learn more, we suggest that you read [Parallels Desktop Licensing Guide](https://docs.parallels.com/landing/pd-ag/parallels-desktop-licensing-guide/).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.parallels.com/landing/pd-ag/getting-started/dividing-users-into-groups.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.