App Home Page View in Zoho Vertical Studio | Vertical Studio Help Guide

App Home Page

In Zoho Vertical Studio, Home Page View lets you design a role-based landing page for your application. You can combine dashboard components and custom views so users see the most relevant business information as soon as they sign in. This functionality allows for the creation of intuitive, at-a-glance overviews of critical business activities and key performance indicators (KPIs) for application subscribers.

For example, in a Real Estate CRM, you can create a Home Page View for the Sales Agent role that shows:
  1. A dashboard component for deals by stage.
  2. A custom view for properties scheduled for site visits.
  3. A custom view for leads that need follow-up today.
This gives agents a working view of active deals, upcoming appointments, and pending outreach as soon as they sign in.

Similarly, in a Healthcare CRM, you can create a Home Page View for the Care Coordinator role that shows:
  1. A dashboard component for patient consultations by status.
  2. A custom view for patients awaiting follow-up.
  3. A custom view for pending care plan reviews.
  4. A custom view for patients referred to other departments by the consulting doctors.
This helps coordinators monitor patient activity, identify delays, and act on urgent requests from a single screen.
You can surface pipeline status, pending follow-ups, open cases, or other high-priority records based on the role assigned to the user.



For more details on Home Page Views, please refer to our detailed guide on Home Tabs.

In the Developer Console, the Home Page View option is located in the left-hand menu under the BUILD category.

To Create a Home Page View: 

  1. In the Developer Console, select Home Page View from the menu and click on + New Home Page.

  2. From the Dashboards section, select the desired dashboards and components you wish to include.

  3. From the Custom View section, choose the views you want to add from various modules.

  4. Drag and arrange the selected components and views to create the desired layout.

  5. Click Save and Share. In the next window:

    1. Specify the Name and description.

    2. Assign the view to the relevant role(s).

Notes
Note

  • Each role can only have one customized Home Page View.

  • If a role does not appear in the list during the configuration process, it may already have an active or inactive Home Page View assigned.

Publish and Version Upgrade

Home Page Views are packaged components, but they are non-upgradable after they are delivered to a subscriber org. A subscriber receives the Home Page Views that are part of the application version available at sign-up time, but later changes to those Home Page Views do not sync to that subscriber.

The following table explains the upgrade behavior of an existing packaged Home Page View already deployed in subscriber organizations. To know more about packaging, please refer to our guide on Components Packaging in Vertical Studio Platform.

Property
Upgrade Type
Subscriber Modify Access
Name
Non-Upgradable
YES

Dashboard Components

Non-Upgradable
YES

Custom Views

Non-Upgradable
YES
Description
Non-Upgradable
YES
Components & View order
Non-Upgradable
YES

Version scenarios

Use the following scenario to understand how non-upgradable Home Page Views behave across sign-up and version upgrade.
Developer action
New Subscriber outcome
Existing subscriber outcome
V1: You create HomePage1 and publish the application.
Subscriber1 signs up for version 1.0 and receives HomePage1.
Not applicable at initial publish.
V2: You modify HomePage1 and add HomePage2.
A new subscriber who signs up for version 2.0 receives the version 2.0 set of Home Page Views, including the latest HomePage1 and HomePage2.
Subscriber1, who already signed up in version 1.0, does not receive the updated HomePage1 or the new HomePage2.
Subscriber1 us upgraded from version 1.0 to version 2.0.
NA
Subscriber1 keeps the previously delivered version of HomePage1 and receives the newly added HomePage2. The version upgrade does not apply updates made to the existing HomePage1.
V3: You delete HomePage2 in the Developer Console and publish.

Existing subscribers are upgraded to the latest version.
Subscribers who sign up for version 3.0 do not receive HomePage2. They receive only the Home Page Views still included in version 3.0.
Existing subscribers who already received HomePage2 keep it in their subscriber org. The deletion does not remove it.

  1. Subscribers can edit the Home Page Views available in their organization.
  2. Subscribers can delete a Home Page View from their organization if they no longer need it.
  3. Subscriber-side edits and deletions stay within that organization and do not affect the packaged definition in the Developer Console.
  4. Developer-side edits and deletions do not overwrite or remove Home Page Views that existing subscribers already have.

Limits and Scalability

  1. Each role can have only one Home Page View.
  2. If a role does not appear when you assign a Home Page View, that role may already have an active or inactive Home Page View assigned.
  3. Home Page Views support up to 20 home page components per organization across Starter, Growth, and Scale plans.
  4. Counts already used in the Developer Console reduce what remains available in the subscriber org. If you consume part of the role limit while building the application, subscribers can use only the remaining role capacity.