> For the complete documentation index, see [llms.txt](https://docs.ixhello.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ixhello.com/ix-hello-reporting/premium-reporting/portal-header-and-product-selector.md).
# Portal Header & Product Selector
The portal header is a Concentrix-branded dark navy bar spanning the full width of the screen. It serves as the primary navigation anchor for the entire Premium Reporting experience.
Figure 1: Portal Header with Product Selector and Hamburger Menu
**Header Components**
**Concentrix Logo:** Displayed at the far left of the header bar, reinforcing brand identity across all reporting views.
**Product Selector Dropdown:** Located immediately to the right of the logo, this dropdown allows users to switch between the three products: IX Hello Employee, IX Hello Customer v1, and IX Hello Customer v2. The currently selected product determines which data and dashboards are displayed throughout the portal. All dashboard tabs, filters, and metrics reflect data for the selected product only.
**Reporting Portal Title:** Centered in the header bar, displaying “Reporting Portal” to clearly identify the application.
**Hamburger Menu Icon:** Located at the far right of the header bar. This three-line icon opens a dropdown menu with user settings, filter management, navigation, and session controls (detailed in Section 3).
---
# 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.ixhello.com/ix-hello-reporting/premium-reporting/portal-header-and-product-selector.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.
