> 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/access-camera.md).

# Access camera

### How can I access the camera in the app?

The app can access the camera only if it is built using your website or renders your website inside the app.

If your website uses the camera, then the app can access it as well. The website link can be added in multiple places within the app, such as Bottom navigation, Menu, page, post, a button on a page or post and more. If the camera works on your website, it can work inside the app.

The same applies to other native features such as location, contacts, microphone, calendar, speech recognition, tracking permission, photos, and reminders. If these features are used on your website, they can also function within the app.

{% hint style="warning" %}
If your app uses any native feature through your website, you must enable the corresponding [**app permission**](/app/download/ios/app-permissions.md) in the build configuration before generating the app build.
{% 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 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.appmysite.com/frequently-asked-questions/app-features-and-settings/access-camera.md?ask=<question>&goal=<endgoal>
```

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