Eternet Portal Documentation
Appearance
Available controls
The page provides a theme toggle and color-palette picker. The chosen appearance affects interface colors and visual presentation, not the data or access policy of backend resources.
Scope
This is a user-interface preference surface; the page does not indicate server-side device, billing, or identity configuration.
Choosing a workspace theme
Appearance settings let a user adapt the portal’s visual treatment to personal preference or workplace conditions. The theme toggle controls the overall light or dark presentation, while the palette picker adjusts the color family used for primary actions, links, and status accents. A consistent palette helps users recognize actions and status cues across Devices, Vehicles, Analytics, and other workspaces. It can also improve comfort for users who work for long periods or in environments with different lighting.
Color selection should not change the meaning of business data. A success state should remain distinguishable from a warning or destructive action in every theme, and the user should not have to rely on color alone to understand status. During a customer presentation, demonstrate the preference change and explain that it affects interface appearance, not a tenant’s stored telemetry, access grants, dashboard configuration, or backend service state. If a chosen palette is not persisted across devices, describe it as a local/session preference rather than a profile-wide setting.
Accessibility and consistency
Theme options are most useful when contrast remains readable for text, borders, focus states, and disabled controls. Customers may have accessibility needs that make high contrast, reduced glare, or clear focus indication important. A visual preference picker should therefore be evaluated across the whole portal, not just the settings page. Check representative tables, maps, charts, dialogs, and status chips after changing the theme. Third-party embedded experiences can follow their own appearance settings and may not match the portal’s chosen palette.
Appearance controls are intentionally separate from authorization and system configuration. A user changing a color theme should not gain access to a resource or alter a shared workspace for colleagues. If the application later stores theme choices centrally, that persistence should be explained separately and verified across sessions. For now, present the page as a personalization surface.
Customer value
Giving users control over theme and palette can make a complex operations portal more comfortable and easier to scan. It encourages consistent visual language and lets organizations align the workspace with user preference while preserving the same underlying features. The best customer demonstration is simple: switch the theme, view a few data-heavy pages, and confirm that text and status remain legible. Do not position the color picker as a white-label branding engine or as a control that changes customer data; those capabilities are outside the current page’s stated scope.
Rollout considerations
For an organization-wide rollout, test the selected themes with the components employees use most often and document any embedded third-party page that follows a separate theme. A consistent appearance is helpful only when status, focus, and error messages remain clear. Preference controls should stay independent from account permissions and operational configuration.