> 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/c159/q519.md).

# Why am I unable to log into or access the cloud version of the app from my desktop/computer?

There are a few reasons why you might be unable to log into the cloud version of the app from your computer:

* If you are not [subscribed](/manual/report-and-run-integrate/quick-start-guide/subscribe.md) to the cloud version of the app, you will not have a cloud account. Report and Run: Offline is a separate system that does not have cloud storage.
* If you *are* subscribed to the cloud version, make sure you are using the same email address when you log into the web portal that you use when you log into the mobile app. 
* If you have never logged into the web portal, you may need to [request a new password](https://app.reportandrun.com/users/password/new).

## Related 

* [FAQ: What are the differences between the cloud and offline versions of the app?](/manual/faq/c142/c143/q388.md)
* [FAQ: How do I get started with a cloud account?](/manual/faq/c142/c144/q394.md)
* [FAQ: Do you have a desktop version of the app for Windows, Linux or Mac?](/manual/faq/c142/c147/q414.md)
* [FAQ: Why isn’t the app syncing across my devices or with the cloud?](/manual/faq/c160/c163/q529.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/c159/q519.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.