As a CRM grows, managing its views gets more complex. List views, Detail Views, and Web Tabs span different modules, each with its own configuration and access settings, making basic admin questions, what views exist, who can access each one, which view a given user actually sees, surprisingly hard to answer without piecing information together from multiple places. Zoho CRM has introduced Pages, a unified way to build, organise, and assign every view in CRM from one place, with per-profile defaults, centralised management, and AI-assisted page creation built in.
Every view in CRM, a list, detail, Kanban, chart, or web tab, is now represented as a Page. Each Page is tied to a module or tab, and every Page can be created, permissioned, and managed from one place under Setup. Previously, different view types were managed through entirely different configuration experiences with no shared model; Canvas pages were configured in Setup while other view types were managed within their own modules. Pages brings these together under one common model.
Associated with a specific module, such as Leads, Deals, or Contacts, representing that module's List and Detail view:
A custom tab not tied to any specific module, buildable using a Link (URL), Widget, SlyteUI, AI, or a Kiosk. Web Tabs were already a standard CRM feature; what's new is that they're now part of the unified Pages model, with the additional ability to build them using AI and associate them with a Kiosk.
When standard views aren't enough for a specific need, highly customised pages can be built using Widgets or SlyteUI components, for example a sales workspace combining pipeline information, target attainment, revenue metrics, and quick actions, or an operations page with custom filters, actions, and external-system information. These are grouped under the Free Style View category, making them easy to identify and manage alongside every other page.
Building a page to match a specific experience previously meant choosing between Widgets, Canvas, and SlyteUI, then assembling and configuring the right components yourself, even when you knew exactly what you wanted. AI offers another way in: describe the experience in plain language, or use a suggested prompt, and CRM turns it into a structured Detail or Web Tab page complete with layout, components, and styling.
For example, typing a request for a lead detail page showing engagement history and every linked record at a glance generates a structured page with a business card header, activity timeline, and related-records layout, which can then be adjusted (switching layout, changing accent colour, adding an Emails component) from the same panel without starting over.
If you'd rather not describe a page from scratch, Presets combine a theme, accent colour, design style, layout, components, and page structure into a ready-made starting point. You can also choose from curated suggestions, or use Surprise Me, which reviews your CRM account and data model to recommend Pages relevant to your team's actual needs rather than generic templates.
A default page determines what a user sees the first time they open a module, or when no saved last-accessed page exists. Rather than simply giving a manager access to a Chart page, you can make it the page they land on when they first open the module; once they access a different page, CRM remembers it and shows that last-accessed page next time. Admins can assign a default page per profile, separately for list and detail views, and for detail views, defaults can be configured separately per layout, so different layouts within the same module can each have their own default.
Timeline, Map, Canvas, System List and Detail, AI-built, Widget-based, and SlyteUI-based pages support standard profile-based access, available to everyone or selected profiles. Two groups differ:
Built-in filters let you narrow pages by module, profile, view type, category, layout, and status, so finding a specific page doesn't mean scrolling a long list. With a bird's-eye view across every module, you can identify unused or redundant pages and deactivate them with a soft, reversible toggle, or delete them permanently.