> For the complete documentation index, see [llms.txt](https://docs.startrail.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.startrail.io/startrail-sdk-js/login-providers/best-practices.md).
# Hints
Guides for the end users
Authentication Request from Web3Auth
Following login providers explicitly requests authentication consent from Web3Auth under Oauth2.0 scheme since Startrail-Sdk-Js makes use of Web3Auth service under the hood.
{% hint style="warning" %}
Please inform your clients to trust the following authenticators, e.g. `Web3Auth`, `openlogin.`
{% endhint %}
| | |
|---|
 | Facebook | |
 | Apple | |
 | Twitter | |
 | Email Passwordless | |
 | Google | |
## Continue Alert Popup
The Continue popup is displayed on the top right side of the screen when a direct login (a single `loginProvider`, no modal) is blocked by the browser's popup blocker. Clicking Continue allows users to proceed with the normal login flow. Sign confirmations are not affected: since v2.3.0 they render inside the wallet iframe (`confirmationStrategy: 'modal'`, the default), immune to popup blockers.
You can also customize the wordings. See more details in [whitelabeling](/startrail-sdk-js/login-providers/whitelabeling.md) page.
---
# 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.startrail.io/startrail-sdk-js/login-providers/best-practices.md?ask=&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.