> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/work-manager/work-manager/user-availability-insights/main-insights-page.md).
# Main Insights Page
The Insights page, available from the main menu, shows a daily breakout of your Insights Data, relating to how time is spent each day. [**Team Members**](#insights-page-for-team-members) use this screen to **view and adjust** their Insights data across a number of days via the calendar control. [**Team Leaders**](/enate-help/work-manager/work-manager/user-availability-insights/main-insights-page-team-leader-features.md#insights-page-for-team-leaders) have these same options, plus additional features available for this page, [detailed here](/enate-help/work-manager/work-manager/user-availability-insights/main-insights-page-team-leader-features.md#insights-page-for-team-leaders).
Team Leaders can use this data to see patterns in how time is being spent through their team, both here and in the [Insights Report.](/enate-help/work-manager/work-manager/user-availability-insights/the-user-insights-report.md) Insights into upcoming availability of their team can also be seen here and such data can contribute to further reports to help with short-term capacity planning.\
\
**Team Leaders should primarily use this page to help ensure all required data has been filled in by their team.**
### Accessing the Insights page
You can access the Insights page from the Nav item option, and via a link at the top of the [Insights Popup](/enate-help/work-manager/work-manager/user-availability-insights/the-insights-popup.md).
## Insights Page for Team Members
### **Main View of Insights Data**
The view defaults to today's date. For each day a user will see in the main section:
* **The 'How are you feeling' value to the day** - this can also be set here, but once set is read-only and comment shows as a mouse-over tool-tip.
* **Data they manually entered on the Insights popup** - or indeed on this same main Insights Screen.
* **Time auto-tracked by Enate** - This is Time which Enate has tracked being spent on the Ticket, Case, Action screen or on an Enate email on this day (includes manual adjustments).
* **The overall total hours -** This is the total combined number of hours input by the user.
These values are grouped into two section showing:
* **'Operational value added hours'** - spent actively performing work for service delivery
* **'Business value added hours'** - spent on supporting activity which indirectly contributes to service delivery
#### Modifying / Adding Insights values
**Modifying Values**
The Insights values (number of hours and minutes) can be modified by users for each day selected.
Users can change all these values manually except for the 'Time auto-tracked by Enate' value, which comes from the Time Tracker control on all work items the users worked on that day (and any work item-related emails they worked on in the Email view). Note that the time tracker data will take manually applied overrides set on work items in preferences to auto-tracked time, wherever they have been entered.
**Click Submit to save any adjustments.**
**Adding missing data**
For days marked as still missing any confirmed data, a message will show at the top of the table. All missing data should be added, including confirming of the Working Hours for that day (a suggested value will often be displayed).
**Click Submit to save any adjustments.**
### Insights Data Displayed
The following data is displayed on the main section, corresponding with the data options shown on the Insights Popup.
* **Working Hours -** Standard amount of working hours for this day.
* **Breaks -** Time spent on breaks, e.g. lunch, throughout this day.
* **Downtime -** Time lost due to, e.g. system issues, or non-availability of work.
* **Time auto-tracked by Enate** - Time which Enate has tracked being spent on the Ticket, Case, Action screen or on an Enate email on this day, (includes manual adjustments).
* **Active time not tracked by Enate** - (only available for historic dates). Time spent actively working to provide service but where a Ticket, Case or Action screen, or Enate email, is NOT open in Enate to auto-track this time.
{% hint style="info" %}
Examples might be: time spent on the Enate homepage or working in another system while an Enate work item tab is NOT open and so not auto-tracking time. *This should NOT include activities such as meetings or training, which should be noted separately.*
{% endhint %}
* **Meetings** - time spent in any collaborative gathering or group meeting.
* **Feedback / 1-2-1** - time spent in individual sessions with e.g. team leader, manager, mentor.
* **Training** - time in organised training or knowledge-transfer sessions.
* **Other** - time spent on any other activities which are not listed above, or any additional breaks taken in a day.
### What counts as a 'day' on this page
A day on the Insights page runs from midnight to midnight **in your own time zone**, and that time zone comes from the **Time Zone** setting on your [User Settings](/enate-help/work-manager/work-manager/user-settings.md) page, not from the clock on your computer.
That matters in three ways:
* If your Time Zone is set to India Time (Kolkata), your Insights day starts at 00:00 in Kolkata, wherever you happen to be sitting.
* If the clocks go forward or back on a day, Insights follows the change. A 23 hour day and a 25 hour day are each treated as one day, with no time counted twice and none lost between the days either side.
* If you are a Team Leader looking at a team member's data, the day you see is **their** day in **their** time zone, not yours. See [Main Insights Page: Team Leader Features](/enate-help/work-manager/work-manager/user-availability-insights/main-insights-page-team-leader-features.md).
To check or change your time zone:
1. Open **User Settings** from your user menu in Work Manager.
2. In **User Profile Settings**, find the **Time Zone** setting.
3. Set it to the time zone you actually work in, and save.
4. Go back to the Insights page and select the date again. The 'Time auto-tracked by Enate' figure is worked out at the moment the page is read, so it updates straight away, for past days as well as today.
{% hint style="info" %}
Enate uses the IANA time zone format. For the full list of time zones you can choose from, see [Time Zones in Enate](/enate-help/work-manager/work-manager/appendix/time-zones-in-enate.md).
{% endhint %}
### Time tracked across midnight
If you keep a work item open across midnight, for example on a night shift, the tracked time is **split between the two days**. Each day gets the share of that time which falls inside it, so your hours land on the day you actually worked them rather than all on the day you started.
A day can never be given more than the clock time of the session that falls inside that day. Here is how that works out in practice:
| What you did | What Insights shows |
| ---------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- |
| Worked on a Case continuously from 23:00 to 01:00, 2 hours tracked | 1 hour on the first day, 1 hour on the next |
| Opened a Ticket at 23:50 and worked on it for 2 hours | 10 minutes on the first day, 1 hour 50 minutes on the next |
| Opened an Action at 13:36 and left it open until 04:23 the next morning, 14 hours 47 minutes tracked | 10 hours 24 minutes on the first day, 4 hours 23 minutes on the next |
| Had a work item open from 23:50 to 01:50 but were only actively on it for 1 hour | 5 minutes on the first day, 55 minutes on the next |
The parts always add up to the total time tracked on that session, so nothing is gained or lost by the split.
{% hint style="info" %}
**The split across midnight is a best estimate, not a measurement.** Enate records when a session started, when it was last updated and how much time was tracked in total, but not which minutes of that session you were active for. Where a session ran unbroken, as in the first three examples above, the split is exact. Where you were away for part of it, as in the last example, Enate spreads the tracked time evenly across the session, and the result is an estimate. Time recorded for Robots is always exact.
{% endhint %}
On the work item itself, a session that runs past midnight is still shown as **one** session on the Time Tracker card, with one start time and one total. It is only the Insights day totals that split it. See [Time Tracking](/enate-help/work-manager/work-manager/work-item-screens/time-tracker-card.md).
### If your hours do not look right
| What you are seeing | What to do |
| ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Hours are landing on the wrong date | Check the **Time Zone** setting on your [User Settings](/enate-help/work-manager/work-manager/user-settings.md) page, as described in [What counts as a 'day' on this page](#what-counts-as-a-day-on-this-page). If it is blank or wrong, set it and select the date again. |
| 'Time auto-tracked by Enate' is higher than the hours you were at your desk | You are likely to have had more than one work item open at once. Every work item you had open accrues time, and Insights adds all of it together for the day. See [Time Tracking](/enate-help/work-manager/work-manager/work-item-screens/time-tracker-card.md) for how to keep auto-tracking accurate. |
| The red message 'Total duration should be less than 24 hours' appears and the day will not save | Your entered hours plus the auto-tracked time come to more than 24 hours for the day. See [Why a day will not save: the 24 hour limit](#why-a-day-will-not-save-the-24-hour-limit) below. |
| You cannot edit the day at all and the fields are greyed out | The day is outside the window you are allowed to edit. See [How far back can I Add / Edit my Insights Data?](#how-far-back-can-i-add-edit-my-insights-data) |
#### Why a day will not save: the 24 hour limit
A day cannot hold more than 24 hours in total. The total that is checked is every value you entered for the day **plus** the 'Time auto-tracked by Enate' figure. If the two together come to more than 24 hours, the page shows **'Total duration should be less than 24 hours'** in red and the day is not saved.
The usual cause is overlapping work: two or more work items open at the same time, each accruing auto-tracked time, or a manual time edit on a work item that is longer than the time actually spent.
To get the day saved:
1. Look at the **Total hours** figure at the bottom of the table and work out how far over 24 hours it is.
2. Reduce the values you entered yourself, for example Meetings, Training or Other, so that the total comes to 24 hours or less. You cannot edit 'Time auto-tracked by Enate' on this page.
3. If the auto-tracked figure itself is wrong, correct it on the work item: open the Time Tracker card on the work item concerned and edit the recorded session time there. See [Time Tracking](/enate-help/work-manager/work-manager/work-item-screens/time-tracker-card.md).
4. Click **Submit**.
{% hint style="info" %}
There is also a limit on each individual value: no single entry, such as Meetings or Training, can be longer than the Working Hours set for that day.
{% endhint %}
### Calendar view
Users can use the calendar control to flip between dates, updating the Insights data displayed in the main section to show data for that date. They also have the following options:
* View and mark dates as 'On Leave', i.e. vacation days (shown in **yellow**).
* View and mark dates as a 'non-working day' for that user, e.g. a weekend day or equivalent (shown in **purple**).
* View dates where their Insights data is currently incomplete (date shown in **RED**). **Use this control to help identify which dates you need to fill in gaps in Insights data.**
*Dates where they can no longer adjust data are shown grayed out.*
#### How far back can I Add / Edit my Insights Data?
Team members can add or Edit Insights data (including setting dates as 'On Leave' or 'Non-Working Day' for up to **7 days in the past**). If you need your data to be adjusted for dates beyond that, speak with your Team Leader who can make necessary adjustment for up to 31 days.
### Entering data in advance
{% hint style="info" %}
Remember that users can enter future Insights data, particularly planned leave and non-working days can be entered in advance if missing, the help Team Leaders withe future capacity planning.
{% endhint %}
---
# 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.enate.net/enate-help/work-manager/work-manager/user-availability-insights/main-insights-page.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.
