> 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/configuring-the-single-sign-on-sso-integration-with-parallels-my-account/troubleshooting-the-sso-activation.md).

# Troubleshooting the SSO Activation

Single Sign-On (SSO) is one of the options offered for activating Parallels Desktop for Mac. Users who choose this option will see a window that looks like this:

<figure><img src="https://content.gitbook.com/content/KtRUprxh035S97pZeygw/blobs/rM1rOCQVpRNqBn35cLyD/07_PDfM_SSO_window.png" alt=""><figcaption></figcaption></figure>

Some users might skip this dialog by clicking **Cancel**. In this case, you can instruct them on how to re-start the SSO-based activation procedure manually. To start the SSO-based activation:

1. In the application's menu, choose Parallels Desktop → Account & License... and select the **Continue with SSO** option.<br>

   **Note**: Users SHOULD NOT enter their corporate login email and password directly on the Sign-In to Parallels Account dialog. They are supposed to log in to their corporate account managed by the Organization’s IdP, not to a Parallels account!

   <figure><img src="https://content.gitbook.com/content/KtRUprxh035S97pZeygw/blobs/GkLOwn1JE3qnbnRF8vPw/SSO_Activate_Edition_Page.png" alt=""><figcaption></figcaption></figure>
2. On the Sign-In to Parallels Account dialog, clicking **Business Edition** (at the bottom of the dialog, on the left) opens the **Activate Business Edition** dialog.<br>

   <figure><img src="https://content.gitbook.com/content/KtRUprxh035S97pZeygw/blobs/hz3lgC4Q3jOpApMR77yS/SSO_License_SignIn_Page.png" alt=""><figcaption></figcaption></figure>
3. On the Enter Enterprise Key dialog, clicking **Continue with SSO** (at the bottom of the dialog, on the left) opens the dialog, which prompts the user to enter the corporate email address. This is where the product activation procedure via Single Sign-On starts!<br>

   <figure><img src="https://content.gitbook.com/content/KtRUprxh035S97pZeygw/blobs/gDt0IDAKOqaNx9e8803w/SSO_License_Deactivated.png" alt=""><figcaption></figcaption></figure>
4. Users should type their corporate email address in the popup dialog that is opened by clicking **Continue with SSO**, then click **Next**.

{% hint style="warning" %}
**Attention**: If a particular user's account still won't activate using SSO, go back to your Identity Provider's settings and make sure that the user is included in the main user group for Parallels Desktop, as described in the [SSO integration setup procedure](/landing/pd-ag/getting-started/configuring-the-single-sign-on-sso-integration-with-parallels-my-account/starting-the-integration-process-in-parallels-my-account.md).
{% endhint %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/pd-ag/getting-started/configuring-the-single-sign-on-sso-integration-with-parallels-my-account/troubleshooting-the-sso-activation.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.
