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

# Dashboard

Right after login to Rubens Admin you see the dashboard view. On top of the dashboard, you will see a "Whats new" section, which gives you an overview of the biggest news in Rubens every quarter.

Depending on the active features of your tenant account, different panels might be shown.

## Rubens statistics

When a configurator is set up for your tenant, the `Rubens statistics` will be displayed in the dashboard. For details on how to use the `configuratorId` see [Embedding Integration](/rubens/rubens-products/rubens-configurator/integration/setup-the-configurator.md#import-the-roomleconfigurator-instance).

The `Rubens statistics` panel gives you an overview of the usages of embedded Rubens configurators. The numbers of `Views`, `Saved configurations` and `3d exports` are displayed for the current month.

* `Views` shows the number of product views in the current period of time. Each time opening a product with the Rubens configurator counts as one view.
* `Conversions` counts the number of checkout calls in Rubens.
* `AR views` shows the number of AR (Augmented Reality) calls. Counts every click on the `Show product in room` button.
* `Saved configurations` is the number of configurations saved for a product using the selected configurator.
* `3D exports` counts the number of 3D exports per product with the selected configurator.

You can see the `Configurator ID` in the panel header next to the time period. If you use multiple configurators within your tenant account, you can choose the configurator in the select box next to the time period.

More analytical data such as for saved configurations can be found under [Analytics](/rubens/rubens-admin/rubens-admin-help/administration.md#analytics).


---

# 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.roomle.com/rubens/rubens-admin/rubens-admin-help/dashboard.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.
