> 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/readme/quick-start-guide/create-an-account.md). # Create an account Set up an account and your first workspace in just a few minutes. 1. Go to 2. Enter your email address and name. 3. Enter and confirm a new password. 4. Read and accept the terms. 5. Click **Create Account**.
6. A green banner will appear at the top of the screen asking you to check your email inbox for a confirmation link.
7. Visit your inbox and open the message from Report & Run. 8. In that message, click **Confirm my account**.
9. You will be taken to the Report and Run login page. 10. Enter your email address and the password you just created. 11. Click **Log in**.
### Create a workspace 1. After logging in, click **Purchase Space**.
2. Enter a title for your workspace. 3. Click **Create**.
### Purchase a subscription 1. Click **Continue** under the purchasing option of your choice: Subscription (monthly), Pre-paid 1 year, or Pre-paid 1 month.
2. Choose your method of payment and complete the payment process.
3. You will see a summary of your subscription when complete.
--- # 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/readme/quick-start-guide/create-an-account.md?ask=&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.