> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/android/bookmarks/bookmark.md).

# Adding bookmarks to documents in Android

Discover how to manage bookmarks effectively with an outline tree in PDFs. Learn to add, edit, and remove bookmarks for a seamless reading experience. The Apryse Android SDK streamlines secure documen

Bookmarks typically represent an outline of a document. Since each bookmark is associated to a specific page, it provides the ability to link to a different page or section in a document allowing the user to navigate interactively from one part of the document to another.

## Get started

[Outline tree](/android/bookmarks/outline.md) An introduction to outline tree.

[User bookmarks](/android/bookmarks/user-bookmarks-a.md) To display a list of user-defined bookmarks that are not available to other PDF viewers.

[Adding a bookmark](/android/bookmarks/add.md) To add a bookmark with color in an existing document.

[Editing a bookmark](/android/bookmarks/edit.md) To edit a bookmark in an existing document.

[Remove a bookmark](/android/bookmarks/remove.md) To remove a bookmark in an existing document.


---

# 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.apryse.com/android/bookmarks/bookmark.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.
