> For the complete documentation index, see [llms.txt](https://help.xaman.app/app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.xaman.app/app/learning-more-about-xaman/how-to-take-a-screenshot.md).

# How to take a screenshot

How to take a screenshot in Xaman

One of the many security features in Xaman is not being able to take screenshots.

Here is how to temporarily disable this security feature.

From the main page in Xaman, press **Settings** then **Security**.

<figure><img src="https://3221812686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMiHAzvIPISVuuzt0AeOR%2Fuploads%2Fgit-blob-066556970629de83276b9668c7d7e54ce279418c%2FBlock%20taking%20screenshots.png?alt=media" alt=""><figcaption></figcaption></figure>

Toggle the switch beside **Block taking screenshots**.

Note: This setting will automatically re-enable when Xaman is restarted.

### How is this a security feature?

All devices have various attack vectors and in the event that your phone was ever comprised, preventing screenshots from being taken in Xaman would prevent an app from sniffing your account secret, your r-address, your balance, etc.


---

# 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://help.xaman.app/app/learning-more-about-xaman/how-to-take-a-screenshot.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.
