> For the complete documentation index, see [llms.txt](https://docs.secureaccess.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secureaccess.com/documentation/user-guide/login-proccess.md).
# Login proccess
When trying to connect to a web application protected by *SecureAccess® CLOUD* (e.g. an intranet portal), the following access window will be shown:
Type your username and press the *Enter key* or click in *Next* button.
Then type your password. If the two-factor authentication is enabled for your account, an extra window will be displayed to link your *SecureAccess® CLOUD* account to your mobile device.
The displayed window depends of the option set by your organization's administrator. There are two types, ***SecureAccess® PUSH,*** ***SecureAccess® TOTP*** and ***Fido U2F.***
### Link your mobile device with ***SecureAccess***® PUSH
If the *SecureAccess® PUSH* has been set as two factor authentication for your account, a new window to link your mobile device will be displayed just after the access window.
Open the *SecureAccess® 2FA* app in your device and scan the QR code displayed by *SecureAccess® CLOUD*, as shown in the following image:
Once the *QR code* has been scanned, the *SecureAccess® CLOUD* account will be linked to your mobile device thought the *SecureAccess® 2FA*. Now click in the *Finish* button.
A notification will be sent to your mobile device to grant access to once the *QR code* has been scanned, the *SecureAccess® CLOUD* account will be linked to your mobile device thought the *SecureAccess® 2FA*.
Since this moment, any new access to a web application through *SecureAccess® CLOUD*, will send a notification to the linked device asking for confirmation. In this way, even if someone knows your credentials, the access to web applications protected by *SecureAccess® CLOUD* will be blocked as he does not have access to your mobile device.
### Link your device with SecureAccess® TOTP
If your user account has been configured to use two factor authentication based in *SecureAccess® TOTP*, a new window similar to the image below will be displayed in the first access to your account.
As first step, open the app in your mobile device and scan the *QR code*.
Once the code has been scanned, your *SecureAccess® CLOUD* account will be linked to your mobile device. The *two-factor authentication code TOTP* for your account will be displayed in the app.
Type the given code in the ***TOTP Code*** field located just below the *QR code* and click the *Finish* button.
At this point your session will be authenticated in *SecureAccess® CLOUD* and the access to web applications of your organization will be granted.
Since this moment, as your mobile device is linked to your *SecureAccess® CLOUD* account, *SecureAccess® CLOUD* will ask for a *TOTP* code before given access to the web applications. A new TOTP code is generated each minute, in this way, even if someone knows your credentials, the access to web applications protected by *SecureAccess® CLOUD* will be blocked as he does not have access to your mobile device.
**Note:** Date and time must be properly set in your mobile device for ensuring the right behavior of *SecureAccess® TOTP.*
## **Link your Fido U2F**
If your user account has been configured to use an Fido U2F usb device, when you have inserted your credentials the system will solicites you to plug in your device.
Click *Next* and your browser will solicite you that confirm clicking your Fido U2F device.
Click your *Fido U2F* confirm button, now your device will be linked correctly.
---
# 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.secureaccess.com/documentation/user-guide/login-proccess.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.