Zoho CRM Layout Rules: Show Fields When You Need Them

Open a lead in most Zoho CRMs and you'll see dozens of fields, most of them irrelevant at that stage. Layout rules fix this. They use a technique called progressive disclosure: as a record moves through your process, users see — and must fill in — only what matters at that point. The result is a cleaner system and better data, without removing any functionality.

Build your first layout rule

Example: hide the detailed lead sections until a lead is qualified, then require address details.

1. Go to Setup → Modules and Fields → Leads → Layout Rules and create a rule (e.g. "Qualified lead").
2. Choose the field that controls the rule — here, Lead Status.
3. Set the condition: Lead Status is Qualified Lead.
4. Action: show sections — pick the sections that should only appear once qualified.
5. Add a second action: set mandatory fields — e.g. Company, Street, City and Country.
6. Save.

New leads now show only the essentials. Change the status to Qualified Lead — even inline, without opening edit mode — and Zoho prompts for any missing mandatory fields, then reveals the extra sections.

Newer layout rule actions

Zoho has been rolling out a much bigger set of actions (availability varies by data centre, so check yours):

• Show pick-list values — filter one drop-down by another. Choose "Partner" as Lead Source and the next drop-down only shows partner options.
• Read-only fields — for example, lock key fields once a deal is Closed Won.
• Set field values — when budget, need and timeframe are all confirmed, set Lead Status to Qualified automatically. Previously this needed a workflow or client script.
• Recommend a field value — suggest a value rather than forcing it. For example, when a product category is chosen on a deal, recommend a closing date based on that category's typical sales cycle.
• Show messages, related lists, buttons and links — hide related lists that aren't relevant to a prospect and show them once qualified, or display a message at the top of the record.
• Verify field — check that values make sense together. If the amount entered is below the minimum spend for the selected product category, the user is told to correct it before saving.

Custom buttons in more places

A related improvement: custom buttons are no longer limited to the top of the record's detail page. In the module editor you can now show buttons on the create and edit pages and on related lists. Buttons can run automations or functions, open widgets or open a URL, and you can choose whether portal users see them.

Practical examples: an "Enrich" button on the create page that looks up a new lead in a data tool such as Apollo while you're entering it; a button that checks whether a new lead already exists in another system; or a "Merge quotes" button on a deal's Quotes related list.

Tips

• Start with the process, not the fields. Map what each stage needs, then build rules around it.
• Don't make too many fields mandatory at once — users will enter junk to get past the prompt.
• Test with a non-admin profile; that's how your team will experience it.

Layout rules pair well with mirrored and roll-up fields for a record page that shows exactly what people need. Watch the August 2026 What's New in Zoho webinar.