> 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.md).

# Access

Access overview

The **Access** category focuses on features that define how users enter and interact with your app. This section includes modules designed to manage and streamline user entry while ensuring compliance and a seamless onboarding experience.

<figure><img src="https://3330324049-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxUo90vXzDtbgOtaUaLYv%2Fuploads%2F22safXPM3ycbLb1JmR9b%2FAccess.jpg?alt=media&amp;token=e7a43016-0718-4fa5-9ff8-635d39c54ec6" alt=""><figcaption></figcaption></figure>

Here’s what you’ll find in this category:

* [**Login & Sign-Up**](https://docs.appmysite.com/app/access/login.md):
  * Guides and resources to help you configure login and sign-up screens, enabling users to create accounts or log in easily.
  * Includes troubleshooting articles to address common issues related to user authentication and account management.
* [**Consent Screen**](https://docs.appmysite.com/app/access/consent.md)**:**
  * Articles explaining how to set up a consent screen to inform users about your app’s terms, conditions, and policies before accessing the app.
  * Covers design and compliance best practices to ensure a professional and legally sound user onboarding process.

Explore the **Access** category for all the information you need to configure user entry points and improve the app experience right from the start.

{% content-ref url="/pages/849zIXUl8BW0R9eSD76A" %}
[Consent](https://docs.appmysite.com/app/access/consent.md)
{% endcontent-ref %}

{% content-ref url="/pages/3A0FEvhQavldW8ll0yqY" %}
[Login](https://docs.appmysite.com/app/access/login.md)
{% endcontent-ref %}


---

# 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.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.
