vSphere Client Design Guidelines

Global Views

A global view can contain a plug-in workflow that does not belong in the object workspace. At minimum, you should place your plug-in's home page in a global view. Another common use for a global view is administration functions, such as configuring your plug-in.

For users to access your global view, you must add a pointer to the Navigator, Shortcuts page, or both.




  • You can use any pattern in the design of a global view.
    Global views are generally consoles and dashboards.

  • Do not exceed two levels of navigation within a global view.
    This will maintain the flat information model. See Navigation Patterns.

  • Do not put object-centric information in a global view.
    Activities that relate to objects belong in the object workspace.


Navigation Patterns

Although you can use any navigation pattern within a global view, a best practice is to use either tabs or a table of contents (TOC) for consistency with vSphere Client. Choose the pattern that best accommodates your space.  You can use these patterns alone or in combination.



Tabs are efficient for navigating through a small number of views.

Tabs must be visible without scrolling. See Tabs in the Clarity Design System for guidance.

Global view with two levels of navigation: tabs and subtabs


Table of Contents

When you have more tabs than can fit in your available space, a TOC is a good alternative.  A TOC can display as many navigation targets as needed.  You can group targets under a heading.

Although a TOC consumes horizontal space, it is easier for users to scan than tabs.

The TOC pattern is used on both the Monitor and Configure tabs in the object workspace. 


Global view with two levels of navigation: tabs and table of contents


SDK Documentation

The extension point for adding a global view to the main workspace is: vise.global.views. See Global Extension Points.