> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.1/vizpads-explore/date-picker-in-filters/customizing-the-calendar-view.md).
# Customizing the calendar view
Learn how to customize the Tellius calendar view by setting the week’s start day, time reference point, and including current dates in time-based queries.
The calendar view can be changed per your requirements. Navigate to **Settings -> Application Settings -> Time Configuration.**
Time configuration
1. Click on the dropdown under **First Day of Week** to change the first day to be displayed in the calendar view.
2. Switch on the toggle under **Time Slices Reference Point** to use your current system date as the reference point.
{% hint style="warning" %}
Tellius uses the **Max Data Date** as default. Switching to the current system date may cause errors if your data is not regularly updated. \
\
"**Max Data Date**" refers to the latest or most recent date present in the data.
{% endhint %}
3. Switch on the toggle under **Include current time** to include the current day as a part of specific time periods (e.g., *show me revenue from the last 7 days* should include today or not?) in search queries.
---
# 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://help.tellius.com/tellius-6.1/vizpads-explore/date-picker-in-filters/customizing-the-calendar-view.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.
