Site-Level Navigation Customization

| Overview

Site-Level Navigation Customisation enhances the portal navigation experience by separating site-specific functions from portfolio-level functions.

Site-specific pages are moved from the portfolio-level 9-dot menu to the site-level hamburger menu. This allows users to remain within the selected site while accessing and navigating between site-specific pages.

The enhancement also introduces customizable navigation, allowing users to pin frequently accessed site pages, access additional pages through a More section, and maintain their navigation preferences across sessions.

| Objectives

The enhancement is designed to:

• Keep users within the selected site context.
• Reduce unnecessary navigation and site re-selection.
• Improve discoverability of site-specific features.
• Provide personalized navigation through pinning and unpinning.
• Clearly separate portfolio-level and site-level functionality.
• Preserve the selected site while navigating between site-specific pages.
• Align migrated pages with the latest portal UI/UX standards.

| Navigation Architecture

The portal navigation is divided into two levels:

Portfolio-Level Navigation

The 9-dot menu provides access to functions that operate across multiple sites or at the portfolio level.

The following features remain in the 9-dot menu:

• User Management
• Quoting Tool
• Portfolio Dashboards
• Portfolio Analytics
• Shared Schedule
• Subscription Details
• Ideas
• DSI Tool Requests
• Help Center
• About

Site-Level Navigation

The hamburger menu provides access to functions associated with the currently selected site.

The following site-specific pages are migrated to the site context:

• Site Manager
• Site Sequencer
• Energy Configuration
• Audit Trail
• Alert Configuration

The hamburger menu also provides access to commonly used site pages such as:

• Site Dashboard
• Scheduling

| Site Context Persistence

When a user enters a site, the selected site becomes the active site context.

When navigating between site-specific pages:

• The selected site shall remain unchanged.
• Migrated pages shall automatically load data for the selected site.
• Users shall not be required to select the site again.
• Site Selection dropdowns shall be removed from migrated pages where applicable.
• Navigation between migrated pages shall not cause loss of site context.
• Site context shall persist until the user explicitly changes the selected site.

Example

If the user selects Site A and navigates:

Site Dashboard → Site Manager → Audit Trail → Alert Configuration

all pages shall continue to display information for Site A without requiring the user to re-select it.

Site Dashboard

Site Manager 

Audit Trail

Alert Configuration

| Default Site Navigation

The default site navigation shall display the following default navigation items:

1. Site Dashboard
2. Scheduling
3. System Operations
4. Zones
5. Easy Street

These default navigation items provide quick access to frequently used site functions.

Additional site-specific pages are available through the More section.

| More Section

The More section provides access to site pages that are not currently displayed as pinned navigation items.

Selecting More opens a flyout containing the available site pages.

The More flyout shall:

• Display both pinned and unpinned pages.
• Allow users to navigate directly to a page.
• Display the current pin state of each page.
• Allow eligible pages to be pinned or unpinned.
• Immediately reflect changes to the user's navigation configuration.

The More section prevents the primary hamburger menu from becoming overcrowded while still providing access to all available site-level functions.

| Navigation Customization

Users can customize their site navigation by pinning or unpinning eligible pages.

Pinning

When a user pins a page:

1. The page is added to the Hamburger menu.
2. The page is removed from the unpinned navigation state in More.
3. The pin icon changes to the filled state.
4. The hamburger menu is updated immediately.
5. The user's navigation preference is saved.

Unpinning

When a user unpins a page:

1. The page is removed from the customizable section of the hamburger menu.
2. The page becomes available under More.
3. The pin icon changes to the outlined state.
4. The Hamburger menu and More flyout are updated immediately.
5. The updated preference is saved.

Users can also unpin a pinned page by right-clicking the navigation item and selecting Unpin.

No page refresh shall be required for pin/unpin operations.

| Pinning Rules

Users can pin up to 8 configurable site pages, excluding permanent navigation items.

Permanent Navigation

Permanent navigation items are always visible and do not count toward the configurable page limit.

The permanent items include:

• Site Dashboard
• Scheduling

Configurable Navigation

Other eligible site pages can be pinned until the maximum limit of 8 configurable pages is reached.

When the limit is reached:

• Additional pin actions shall be disabled.
• A tooltip shall explain that the maximum number of pinned pages has been reached.
• Unpinning an existing page shall immediately make a slot available.
• The newly available slot can then be used to pin another page.

| Navigation Order

Pinned pages shall retain the display order associated with the user's customization preferences.

When the user returns to the portal or starts a new session:

• Previously pinned pages shall be restored.
• Their configured order shall be retained.
• Unpinned pages shall remain available through More.

Navigation preferences are user-specific and shall not affect other users.

| Navigation Indicators and Tooltips

The navigation UI shall provide visual indicators for the current pin state.

The icon state shall update immediately following a pin or unpin operation.

Tooltips shall be provided for:

• Navigation items where additional information is useful.
• Pin/unpin actions.
• Disabled pin actions when the maximum pin limit has been reached.

| User Preferences

Navigation customization shall be stored against the user's preferences.

The system shall persist:

• Pinned pages.
• User-defined pinned page order.
• Pin/unpin state.

When the user logs in again:

1. The user's saved navigation preferences are retrieved.
2. The hamburger menu is reconstructed based on those preferences.
3. Permanent navigation items are displayed.
4. Configured pinned pages are restored.
5. Remaining eligible pages are available through More.

User A's navigation configuration shall not affect User B's configuration.

| Permissions and Access Control

Navigation visibility shall continue to respect the user's existing permissions.

If a user does not have access to a particular site-level feature:

• The feature shall not be exposed as an accessible navigation option.
• Existing authorization rules shall continue to control page access.
• Navigation customization shall apply only to pages available to the user.

Pinning a page shall not grant the user any additional permissions.

| High-Level Functional Flow