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

# Login and Dashboard

#### What You'll Need

* Your Insuraviews account credentials
* A modern web browser (Chrome, Firefox, Safari, or Edge)
* Basic understanding of insurance rate filings

#### First Login

1. Navigate to [app.insuraviews.com](https://app.insuraviews.com/)
2. Enter your credentials
3. You'll be taken to your main dashboard

<figure><img src="https://3627719227-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRDo7Wvsasy8Pyg5liYJv%2Fuploads%2FmJs3FUcLePRafp75a0Uj%2FInsuraviews%20Dashboard%20edited.png?alt=media&amp;token=88610674-75a8-4736-ad93-991512db045e" alt=""><figcaption><p>Insuraviews Dashboard</p></figcaption></figure>

### Dashboard Overview

Your Insuraviews dashboard is your command center for market intelligence.&#x20;

Here's what you'll see:

* **Search:** Access our powerful rate filing search engine, with suggested search terms
* **Recent Filings:** Shows the 6 filings added most recently, with some basic filing information and the date added
* **DOI Reviewers Top 10 List:** Shows top 10 reviewers based on their average days to approve filings
* **AI Insights:** Ask our custom AI assistant about insurance topics or filings to take a deep dive into our structured data
* **Navigation Sidebar:** Select one of our reports or tools to dive deeper into rate filings
* **Updates:** See what features and changes are being added to Insuraviews


---

# 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.insuraviews.com/getting-started/quickstart.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.
