> 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/frequently-asked-questions/app-features-and-settings/control-access-to-app.md).

# Control access to app

### Can I control who has access to my app and its content?

While you cannot directly restrict access to your app or its content, you can take user consent before granting access.

If users don't accept the terms of 

To enable this feature, go to the [**Access**](https://app.appmysite.com/app/consent) module and turn on the toggle for **"Ask for User Consent."** This ensures users provide consent before accessing mature themes or sensitive content.

If users don’t accept the terms of the consent, they will likely choose the close app button, which will exit them out of the app.

For a detailed guide, follow the link below: 

{% content-ref url="/pages/Q37UOj7mDihjKDDD5bFW" %}
[Add consent screen](/app/access/consent/add-consent-screen.md)
{% endcontent-ref %}

{% hint style="success" %}
This feature also helps you comply with statutory or regulatory requirements related to your app’s content by Google Play and Apple App Store.
{% 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/frequently-asked-questions/app-features-and-settings/control-access-to-app.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.