> 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/ras-user-portal-guide/v19/using-google-authenticator.md).

# Using Google Authenticator

To use Google Authenticator, you need to install the Authenticator app on your iOS or Android device. Simply visit Google Play or App Store and install the app. Once the Authenticator app is installed, the user is ready to connect to Parallels RAS using two-factor authentication.

To connect to Parallels RAS:

1. The user opens Parallels User Portal and log in using your credentials.
2. The multi-factor authentication dialog opens displaying a barcode (also known as QR code) and a secret key.
3. Opens the Google Authenticator app on your mobile device:
   * If this is the first time you use it, tap **Begin** and then tap **Scan a barcode**.
   * If you have already created another account in Google Authenticator, tap the plus-sign icon and choose **Scan a barcode**.
4. Scan the barcode displayed in the Parallels Client login dialog.

   If scanning doesn't work for any reason, go back in the app, choose **Enter a provided key,** and then enter the account name and the key displayed in the Parallels Client login dialog.
5. Taps **Add account** in the app, which will create an account and display a one-time password.
6. Go back to Parallels Client, click **Next,** and enter the one-time password in the **OTP** field.

On every subsequent login, you will only have to type the credentials (or nothing at all if the **Save password** option was selected) and enter a one-time password obtained from the Google Authenticator app (the app will continually generate a new password).


---

# 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/ras-user-portal-guide/v19/using-google-authenticator.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 `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.