> 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/parallels-desktop-enterprise-quick-start-guide/end-to-end-implementation-stages-technical-workflow/stage-1-account-sso-and-licensing-configuration.md).
# Stage 1: Account, SSO & Licensing Configuration
### What this stage accomplishes
Registers your license to a Parallels Business Account, sets your activation method(s), and divides your users into groups with sublicenses so later stages have something to target.
License activation does two things: it unlocks Parallels Desktop's functionality, and it connects that installation to your organization's Parallels Management service — which is what lets the Portal push a Golden Image and Policy to it later ([Stage 3](/landing/pd-ag/parallels-desktop-enterprise-quick-start-guide/end-to-end-implementation-stages-technical-workflow/stage-3-management-portal-and-remote-policy-setup.md), [Stage 4](/landing/pd-ag/parallels-desktop-enterprise-quick-start-guide/end-to-end-implementation-stages-technical-workflow/stage-4-enterprise-deployment-jamf-pro-intune-email.md)).
### Prerequisites
None — this is the first stage. If you're setting up SSO, you'll additionally need admin access to your email domain's DNS host (to add a verification TXT record) and admin access to configure enterprise applications in your identity provider (or someone who has it).
### Steps
1. **Create a Parallels Business Account and register your license.** Go to [my.parallels.com](https://my.parallels.com/login), select **I am a new user** (or log in if you already have one), and register your Enterprise Edition license.
2. **Decide your activation method(s).** License-key activation and SSO both work on the same license, and Enterprise Edition lets you mix per-device (license key) and per-user (SSO) activation across the same setup.
3. **If using SSO**, complete the domain verification (DNS TXT record) and configure the enterprise application in your identity provider (Azure/Entra ID, Okta, etc.).
4. **Divide users into groups with sublicenses.** In My Account, open **Dashboard** → your Enterprise Edition card → **Subscription Details** → **License Keys** → **Create License Key**. Name it for the group, assign a seat count, and choose **Dynamic** or **Reserved** as the key type.
5. **Don't hand out your primary license key.** Use the **Invite Users** button (for license-key activation) or sublicense-to-SSO-group mapping instead — this keeps a compromised key isolated to one group instead of your whole license.
{% hint style="warning" %}
**Attention**: Each group gets exactly one policy later on (Stage 3), so plan your groups around how you actually want to differentiate Golden Images and Security Controls, not just around org chart lines.
{% endhint %}
### Verification
In My Account, confirm your license card shows the correct product type (Enterprise Edition) and seat count, and that each sublicense you created appears under **License Keys** with the right name and seat allocation.
### Common issues
DNS TXT record propagation can take a while before SSO domain verification succeeds. Sending your primary license key to end users directly is a common mistake — if it leaks, you can't just revoke one sublicense.
### Handoff to next stage
With your groups and sublicenses in place, move to Stage 2 to prepare the Golden Image (or Declarative source) and, if you need Intune enrollment, the provisioning package.
---
# 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/parallels-desktop-enterprise-quick-start-guide/end-to-end-implementation-stages-technical-workflow/stage-1-account-sso-and-licensing-configuration.md?ask=&goal=
```
`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.
