By the CodeStringers Team — Zoho Experts & Custom Software.
A sales manager we work with used to start every Monday the same way: open the Deals module, scroll past a few hundred records that had nothing to do with her team, then eyeball which ones were slipping. It took twenty minutes and she still missed deals. The fix wasn't a new report or an add-on — it was a saved custom view her reps could open in one click. That's Zoho CRM custom views explained, in one sentence. If you're weighing that kind of cleanup across a whole org, it's the everyday work our Zoho CRM consultants do before anyone talks about dashboards or automation.
A custom view in Zoho CRM is a saved, filtered version of a module's list — its own set of criteria, its own columns, its own sort order, shared with exactly the people who should see it. It lives inside the module (Leads, Deals, Contacts) and answers one question well: which records matter to this person, right now?
That distinction matters because of where sales time actually goes. Salesforce's State of Sales research found reps spend less than 30% of their week actually selling — the other 70-plus percent disappears into admin, data hunting, and internal busywork (source: Salesforce State of Sales research, 2023). A view that surfaces the right ten records instead of ten thousand is a small dent in that number, and small dents add up.
Before building anything, figure out which tool you're reaching for. People conflate three different things.
The default list view is what a module shows out of the box. You can reorder or hide columns on it, but you can't save a filtered slice as its own named thing.
A custom view is a named, saved, filtered list — the workhorse this article is about.
A styled or Kanban view changes how records look (cards, tiles, columns-by-stage), not which records qualify. Different job entirely.
The rule of thumb: if you're changing which records appear, you want a custom view. If you're only changing how they're arranged on screen, stay in the list or Kanban view. Getting that wrong is the most common reason people think custom views are "broken" — they built a Kanban board and expected it to filter.
Criteria are the filter — the set of rules that decides which records qualify. Zoho CRM lets you stack up to 25 criteria in a single view, combined with an AND/OR pattern editor and brackets to control precedence (source: Zoho help: List view). Without brackets, the system reads a pattern like ((1 or 2) and 3), so grouping is worth getting right.
A pattern our team leans on for a "my active pipeline" view looks like this:
(Owner is <current user>)
AND (Stage is not Closed Won)
AND (Stage is not Closed Lost)
AND (Closing Date is in the current fiscal quarter)Two field-behavior details save real debugging time:
Owner-based criteria travel. If you set the owner to the logged-in user rather than a named person, one shared view works for the whole team — each rep sees only their own records. You build it once.
Cross-module criteria exist now, and they're powerful. Zoho added support for filtering a module by fields on related modules or subforms — up to 3 related modules or subforms per view, with up to 3 fields per module (source: Zoho help: Empowered custom views cross module criteria now supported in Zoho CRM). That means a Deals view can filter on the linked Account's industry or region without a workflow or a formula field doing the join for you.
That last one quietly retires a lot of the custom fields people used to create just to make records filterable.
Criteria decide which records show; columns decide what you see about them. In the view editor you drag the fields you want into the display, in the order you want them, and Zoho's own guidance is to keep it under 10 columns so the list doesn't force horizontal scrolling (source: Zoho help: List view).
Sorting is per-column and lives on the list itself: click a column header to sort ascending or descending. One practical note from building these at scale — sort by the field that drives the daily decision, not the record name. A collections view sorted by days overdue descending puts the fire at the top. Sorted alphabetically by company, it hides it on page 4.
A good custom view answers one question in one screen. If it needs a scrollbar and a second glance, it's really two views.
This is where custom views stop being a personal convenience and become an operations tool. When you save a view, Zoho gives you three sharing scopes: show it only to you, show it to all users, or share it with selected recipients — and "selected" lets you pick Users, Groups, Roles, or Roles and Subordinates (source: Zoho help: List view).
The scope you choose has real consequences, so match it to the org chart:
Share scope | Who gets it | Best for |
Only me | Just you | Personal working lists, drafts |
All users | Everyone with module access | Company-wide standards ("Open Deals This Quarter") |
Selected: Roles / Roles & Subordinates | A role and, optionally, everyone reporting under it | A manager plus their team, without naming each rep |
Selected: Groups | A defined group of users | Cross-functional squads (e.g., a deal desk) |
Two things worth building into your standard operating procedure. First, when you share a view, Zoho exposes a Lock this view option — check it and the recipients can use the view but can't quietly rewrite its criteria, so your "official" pipeline definition stays official. Second, sharing a view is not the same as sharing the records in it; visibility of the underlying records is still governed by your roles, profiles, and data-sharing rules. A rep only ever sees the records they're already permitted to see, filtered by the view — never more.
If your role hierarchy and sharing rules aren't clean, this is exactly the moment to fix them, and it's a core piece of what our Business systems consultant work sorts out during an implementation.
Book a free Zoho consultation and we'll audit your current views, roles, and sharing model in one session — start with a no-risk discovery call.
Here's the Monday-morning problem from the top of this article, solved as one view on the Deals module:
Criteria: Stage is not Closed Won AND Stage is not Closed Lost AND Closing Date is before Today AND Amount is greater than 5000. That's four rules — well inside the 25-criteria ceiling — surfacing open deals that should have closed and are big enough to chase.
Columns: Deal Name, Account Name, Amount, Closing Date, Owner, Stage. Six columns, no horizontal scroll.
Sort: Closing Date, oldest first — the most overdue deals rise to the top.
Share: to the Sales Manager role and subordinates, with Lock this view on, so the definition of "at risk" is the same for every rep and can't drift.
That view replaced a twenty-minute manual scan with a one-click list, and it's the kind of quiet operational win that adds up. Nucleus Research pegs the average return on CRM at $8.71 for every dollar spent — but that number only shows up when people actually use the system, and people use what's fast to look at (source: CRM pays back $8.71 for every dollar spent). When the right records are one click away, adoption stops being a fight.
One giant view for everyone. A 15-criteria monster that tries to serve sales, support, and finance serves no one. Build focused views per role.
Naming records instead of owners in criteria. Hard-coding "Owner is Jane" breaks the moment Jane changes teams. Use the current-user token.
Skipping the lock. Shared, unlocked views drift — three months later everyone's "pipeline" means something slightly different.
Reaching for a custom module or field. With 25 criteria and cross-module filtering, most "we need a new field to filter on" requests are actually just a smarter view. If you do genuinely need engineered logic beyond what views offer, that's where custom software development picks up — but check the view first.
Custom views are the highest-leverage, lowest-cost customization in Zoho CRM: criteria decide who qualifies, columns and sort decide what you read at a glance, and role- or group-based sharing (with a lock) turns a personal list into a team standard. Master the four moving parts — criteria, columns, sort, sharing — and you've solved most of the "our CRM is cluttered" complaints without a single line of code. When the cleanup runs deeper than views can reach, book a free Zoho consultation and we'll map it with you — start a no-risk discovery call.
CodeStringers is a custom software engineering firm with a dedicated Zoho practice, writing from work we've actually shipped for clients.
For more on shaping Zoho CRM to your team, see our guides to Zoho CRM assignment rules and Zoho CRM page layouts.
In a no-risk discovery we look at your CRM, finance and operations systems and who owns each part, and show what a connected system would do differently. You pay only if you proceed. Or see how we approach it.
More on the same problem:
Zoho CRM Custom Module vs Subform: How to Model Related Data (Without Repainting Later) (article)
Zoho CRM Canvas View Explained: What It Is and How to Use It (article)
The Field You Add Today Is The Migration You Pay For Later | Zoho CRM Custom Fields (video)
A custom view is a working list: records to act on now, with mass actions available from the list. A report is for analysis: grouping, summaries, charts and scheduled delivery. If the question is which deals do I call today, build a view. If the question is how many deals closed by source this quarter, build a report. Views live inside the module; reports live in the Reports tab and can feed dashboards.
Yes. Selecting records in a view exposes mass update, mass email, mass delete, change owner and macros, which is why a precise view is a productivity tool. A collections view of overdue invoices becomes a one-click reminder batch. Lock the shared views that drive mass actions so the criteria cannot drift, and keep delete rights narrow, because a mass action on a wrongly filtered view affects every record in it.
Date fields can be filtered with relative values such as today, this week, last 30 days or current fiscal quarter, which keeps a view current without editing it. A view for deals closing this month rolls forward automatically. Combine relative dates with the current user token for owner so one shared view serves every rep every month. Avoid fixed dates in shared views; they stop working the day after the period ends.
Yes. Views created on the desktop appear in the mobile app for the same module, with the same criteria, and users can mark favorites so their daily lists are one tap away. Column choices are simplified on a phone, so set the first few columns to the fields a rep needs in the field. Build the view on the desktop and check how it reads on a device before sharing it.
Zoho CRM allows a large number of views per module, and the practical limit arrives earlier: a module with forty views becomes hard to navigate and nobody knows which one is official. Keep a short set of shared, locked views per role, let users create personal views freely, and review the shared list quarterly. Delete shared views that no one has opened in months.
"Something isn't working." "We're outgrowing our tools." "We're afraid to make the wrong move." No-Risk Discovery is a short, practical conversation that gets you clarity before you commit to anything big. We'll tell you if we're a fit. If we're not, we'll tell you that too.
Say who you are and ask. A person replies within one business day.
