> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/cerby-mobile-app/collections/managing-your-collections/view-your-collections.md).

# View your collections

This article describes how to access and view your collections and subcollections in the Cerby mobile app.

{% hint style="info" %}
**Who can use this feature?**

* Workspace **Owners**, **Super** **Admins**, **Admins**, **Users**, and **Guest** **Users**
* Collection **Owners** and **Collaborators**
* Supported using the Cerby web app, browser extension, and mobile app

**NOTE:** Read more about Collections in Cerby in the article [Collections](https://help.cerby.com/getting-started/concepts/credential-management/collections)
{% endhint %}

As a collection **Owner** or **Collaborator**, you can see how your items are organized in collections and subcollections using the Cerby mobile app.

The **Collections** screen shows the following information:

* The names of your collections
* The number of items and subcollections within it, if it’s not empty

To view your collections, you must complete the following steps:

1. Open the Cerby mobile app on your mobile phone.
2. Log in to your Cerby workspace.
3. Activate the **Collections** tab located at the top on iOS or tap the **Collections** button located at the bottom navigation bar on Android. The **Collections** screen is displayed.\
   **NOTES:** Consider the following when viewing your collections:
   * To view the items within the collection, tap the collection card.
   * Collections and subcollections are displayed at the same level; however, if a collection contains subcollections, they are displayed within the collection.

***


---

# 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.cerby.com/cerby-mobile-app/collections/managing-your-collections/view-your-collections.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.