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

# How do I view the end date of my subscription?

You can see your subscription end date in the mobile app or web portal. 

From the mobile app, tap the three horizontal lines in the top-left corner to open the main menu. Then tap on your company information (name, image count, user count) at the top of the menu. You will see your current subscription details.

From the web portal, open your workspace and [click on Current Subscription](/manual/readme/account-management/show-current-subscription.md). 

## Related

* [Article: How to show current subscription details on the web portal](/manual/readme/account-management/show-current-subscription.md)
* [Article: How to upgrade/downgrade your monthly subscription in the web portal](/manual/readme/account-management/upgrade-downgrade-your-account.md)
* [Article: How to upgrade/downgrade your pre-paid account in the web portal](/manual/readme/account-management/upgrade-downgrade-your-account-1.md)
* [FAQ: How do I reactivate my subscription after it has expired or been cancelled?](/manual/faq/c167/q561.md)
* [FAQ: How do I download invoices or receipts for my subscription payments?](/manual/faq/c167/q564.md)
* [FAQ: Why is my subscription showing as inactive?](/manual/faq/c160/c165/q543.md)


---

# 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.reportandrun.com/manual/faq/c167/q568.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.