> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/app/access/login/prompt-user-login.md).

# Prompt user login

### How to enable login prompt on app launch?

If you would like to prompt users to log in to your app as soon as it launches, you can enable the login prompt setting. This ensures that users must authenticate themselves every time they access the app.

{% hint style="warning" %}
This feature is available for apps built using the WordPress, WooCommerce, and Custom App product. 
{% endhint %}

{% embed url="<https://scribehow.com/shared/Enable_login_prompt_on_app_launch__UD3clDJyT6Ki_z99P8BcGw>" %}

* Navigate to the Login Settings:
  * Log in to your AppMySite account.
  * Go to [**Access > Login**](https://app.appmysite.com/app/login) in your dashboard.
* **Enable the Login Prompt**:
  * Click on the Settings icon at the top right of the Login screen.
  * Toggle on "Prompt login on app launch."

Click Save to apply changes.&#x20;

#### **What Happens When This Feature is Enabled?**

* Users will be prompted to:
  * Log in
  * Register
  * Browse as a guest
* If the toggle is disabled, users will be directed to the app home screen upon launch. They will only be asked to log in or register during specific actions, such as checkout.

{% hint style="warning" %}
This feature requires at least one login method to be enabled before the login prompt toggle becomes available.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmysite.com/app/access/login/prompt-user-login.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.