DEV Community: Skyfall

Zoho CRM territory management: setup and pitfalls

Skyfall — Thu, 05 Nov 2026 23:16:04 +0000

Disclosure: I work at Skyfall Labs, an official Zoho Partner, so I have a commercial interest. The facts below are from Zoho's own help pages, linked at the end; advice is labelled as advice. Originally published on skyfallhq.net.

When sales teams share accounts across regions, industries or product lines, role hierarchy alone can feel too rigid. Territory management groups accounts by their characteristics instead of only by owner. This post sets out what Zoho's pages say, including choices that cannot be undone.

What it is, per Zoho

Zoho says a territory groups customer accounts within the sales force structure so they can be shared with sales staff, and that territories can be based on geography, industry, product line, expected revenue or verticals. Zoho says users with the Administrator profile can enable the feature. The overview page does not name editions, so check feature availability for your edition.

Roles versus territories, per Zoho's decision guide

Both models give each record one owner. With roles, a record is visible to its owner, users above in the hierarchy and users granted access by sharing rules; with territories it is also visible to other users in its territory and to users in territories above it.
A user can hold only one role but can belong to multiple territories.
With roles a user gets a single forecast target; with territories, one per territory they belong to, and switching changes forecasts to suit territory requirements.
Zoho says territory management need not be a requirement for every organization and that the choice depends on your sales structure and sharing model.

Setup, per Zoho

Go to Setup, Security Control, Territory Management and click Get Started.
Choose Start from Scratch or Extend from Role Hierarchy (which copies roles into territories). Zoho says you cannot switch between these two options after choosing.
Once enabled, leads, contacts, accounts and deals get a Territories field and territory-based forecasts become available.
Create territories under Territories, Create New Territory: name, manager, parent territory, users with Read Only or Read/Write/Delete permission (shared by all users in the territory), and rule criteria.
Deal and Lead Territory Rule settings must be enabled before rules can be added for them.

Rules and limits, per Zoho

Records are assigned automatically when created or modified and they meet the criteria; a record is not assigned to a sub-territory unless it also meets the parent territory's criteria.
An account or contact can belong to a maximum of ten territories; a deal can belong to only one.
Territory managers and administrators can assign records manually.
Deleting a territory permanently removes its details, and sub-territories must be moved under another parent.
Disabling makes territory information in accounts, contacts and deals inaccessible and permanently deletes existing territory-based forecasts; re-enabling keeps the territory structure.
The page does not state a maximum hierarchy depth.

Pitfalls (practical advice)

This section is advice from experience, not vendor documentation.

Decide on roles versus territories before enabling: the start-from-scratch or extend-from-roles choice is permanent per Zoho, and disabling deletes territory forecasts.
Write the territory criteria on paper first (for example, which field decides a region) and check that the underlying data is consistent, or rules will assign records unpredictably.
Because a sub-territory needs its parent's criteria met too, design parent rules broad enough to contain their children.
Rehearse in a sandbox and review forecast settings with the sales manager first.

Sources

Zoho CRM dependent picklists: cleaner, consistent data

Skyfall — Thu, 05 Nov 2026 23:05:34 +0000

Messy free-choice dropdowns lead to reports that cannot be trusted: the same thing recorded three ways. Zoho offers Map Dependency, where the options in one field depend on the value of another, and global sets, which share one list across picklists. This post sets out what Zoho's pages say.

Map Dependency, per Zoho

Zoho describes a parent-child relationship: Map Dependency controls which child-field options appear for each selected parent option.
Parent and child can be any option-based field in the layout or subform: picklist, multi-select picklist or radio button. Multi-select picklists can only be child fields, and a child can also be a parent in another mapping.
The layout must contain at least two option-based fields. Subform parent fields can only map to fields in the same subform.
It needs administrative privileges. Setup path: Setup, Customization, Modules and Fields, open the module, Map Dependency Fields.
Steps: Create Map Dependency, select the layout, parent field and child field, map the values, check the Preview screen and Save. After saving, child values change with the parent when records are created or edited.
Zoho's page gives a search bar for more than 10 options and an Advanced view for 50 or more options.

What that page does not say

The Map Dependency page I read does not state a maximum number of dependency levels or mappings, the effect on existing records, API support, or which editions include it. Check these in your own account before relying on them.

Global sets, per Zoho

Global sets are collections of picklist values that can be associated with multiple picklists across modules. You can link only the whole set to a picklist, not parts of it.
Zoho says changing a global set value updates it in all associated picklists and in existing records, workflow rules, field updates and reports.
A picklist can be switched from local values to a global set and back. Values present in both are mapped automatically; local values missing from the set must be mapped manually.
Users need the Modules Customization permission. Zoho lists limits by edition on the page; check them for your edition.

Layouts also affect what people see

Zoho's page-layouts FAQ says the picklist values a user can see depend on their layout access: with 3 layouts and 5 values each for a picklist, a user with access to 2 layouts sees 10 values.

Pitfalls (practical advice)

This section is advice from experience, not vendor documentation.

Agree one list of values with the people who use the reports before building dependencies; changing a messy list is harder than starting clean.
Prefer a global set where several modules need the same list, so one change is made once.
Test a dependency on a few records in a sandbox first, and check how existing records with now-invalid combinations behave in your account.
Keep dependency chains short so users are not forced through long cascades of dropdowns.

Sources

Zoho CRM layout rules: simplify cluttered screens

Skyfall — Thu, 05 Nov 2026 22:56:54 +0000

A common complaint is that Zoho CRM record screens are crowded with fields most people never need. Zoho's layout rules let a form show sections or fields, or require fields, only when another field has a certain value. This post sets out what Zoho's pages say, including the limits that surprise people.

Page layouts versus layout rules

Zoho's page-layouts FAQ says layouts are given to profiles through Layout Permission and Layout Assignment, and that a profile can access several layouts but has only one default. The same FAQ names not being on the Enterprise Edition, or lacking the Customize Zoho CRM permission, among the reasons you may be unable to create a layout (it does not say whether higher editions qualify). Layout rules work inside a layout: Zoho's Kaizen post says a rule is built on a layout, a primary field and a condition.

Zoho's pages I read do not state which editions include layout rules, so check feature availability for your edition.

What a layout rule can do, per Zoho

Actions are Show Fields, Show Sections, Set Mandatory Fields and Show Subforms.
Conditions on the primary field are: is, isn't, contains, doesn't contain, starts with, ends with, is empty and is not empty.
One condition can trigger several actions. A condition can have at most five criteria, combined with AND or OR; the primary field can be used in only one criterion, and that one can only be joined with AND.
To create one, go to Setup, Customization, Modules, select the module, and use the Layout Rules section. Only users with the Customize Zoho CRM profile permission can access it.
Rules apply on the create, edit and view pages.

Limits and where rules do not apply, per Zoho

Record Owner and multi-select picklist fields cannot be the primary field.
Layout rules cannot use Auto Number, Lookup, Multi Select Lookup, User Lookup, Formula, File Upload or Multi Line fields.
Layout rules are not available for records created through import, web forms or the lead convert page.
Through the API, only mandatory-field rules apply (with the apply_feature_execution key). Show Field, Section and Subform rules are not supported there; Zoho notes that records can hold values in hidden fields and that the Get Records API returns all fields in the layout.
A field that is the primary field of one rule cannot be the primary field of another rule.

Pitfalls (practical advice)

This section is advice from experience, not vendor documentation.

Hidden does not mean empty: per Zoho, hidden fields can still hold values, so do not treat hiding as a way to clean data.
Because imports, web forms and lead conversion skip layout rules, records from those routes may not follow the same required-field logic as manually created ones. Check those routes after designing a rule.
Start from the job people do on the screen, list the fields they actually need at each stage, and build the smallest set of rules that gets there.
Test changes in a sandbox before rolling them out to every user.

Sources

Zoho CRM audit log: find who changed what

Skyfall — Thu, 05 Nov 2026 22:38:40 +0000

When a field value changes, a workflow is edited or records vanish, the first question is who did it. This post sets out what Zoho's help pages say about the audit log and picklist history tracking.

What the audit log is

Zoho describes the audit log (or audit trail) as a record of all the actions each user in your CRM account performs, in chronological order. Zoho contrasts it with a record's Timeline, which covers one record and cannot be exported; the audit log covers all records and can be exported as a CSV file.

What it records, per Zoho

Record actions in modules such as Leads, Accounts, Contacts, Deals and Activities: create, update, delete, import, lead conversion, restore and similar.
Setup actions, including templates, workflow and auto-response rules, webhooks, roles, profiles, groups, reports, assignment rules and users.
Bulk actions such as mass update, mass delete, import, export and restoring from the recycle bin.
Workflow changes show who made the change, when, which workflow and the rule name, with View changes for details.
Login history is not in the audit log; Zoho points to Setup, Security Control, Login History.

Who can view it and how to use it

Zoho says admins and users with the CEO role can access the audit log, while non-admin users see only their own actions and those of their subordinates. You can filter by entity, user, action type and date range. Zoho's FAQ places it under Setup, Security Control, Audit log, with Export Audit Log on the right-hand side; your menu may differ, so check your account.

Limits Zoho states, and a conflict to check

Zoho's FAQ says the audit log captures only actions from the last 3 years, that older actions are permanently deleted, and recommends exporting periodically for a permanent record. However, Zoho's data backup page refers to investigating changes and deletions in the audit log for up to 60 days. The two pages disagree, so check your own account rather than relying on either figure. Neither page states edition availability; check feature availability for your edition.

Field-level history: picklist tracking

Zoho says picklist history tracking can be enabled for one picklist field per module, from the field's properties, by users with the Module Customization permission.
The history related list shows picklist values, duration, modified time, modified by and moved to, plus up to 10 additional fields. Deals already show a default stage history.
It is not supported in Tasks, Calls or Meetings.
Zoho says that if tracking is disabled or the tracked field is deleted, all tracked data is lost permanently, and that a customer-initiated edition downgrade deletes history tracker data immediately.

Using it well (practical advice)

This section is advice from experience, not vendor documentation.

When something changes unexpectedly, filter the audit log by module, action and date range first, then by user.
Export the log on a schedule you set, rather than relying on retention.
Decide which one picklist per module matters most for history (often a stage or status) before enabling tracking.
Name workflows and rules clearly, so log entries are readable.
Use the log findings to fix the process or permissions, not only to find a person.

Sources

Zoho CRM backup and recycle bin: what you can recover

Skyfall — Thu, 05 Nov 2026 22:28:06 +0000

Most teams learn how Zoho CRM recovery works after someone deletes records. This post sets out what Zoho's help pages say about the recycle bin and data backup, including the time windows Zoho states.

The recycle bin

Zoho says records and files deleted from the account are stored in the recycle bin, and you can restore them within 60 days, after which they are permanently deleted. Items can also be permanently deleted from the bin early. The path is Setup, Data Administration, Recycle Bin: select items and click Restore, or Delete to remove them permanently; a filter helps with large volumes. Zoho says what you see depends on your role hierarchy and your permission to view the records.

The pages do not say how related records are handled on restore, or whether availability differs by edition. Check feature availability for your edition.

Data backup, per Zoho

Users with an administrative profile can request a backup. Zoho notes the revamped process is available only to select users in certain data centers, so check your account.
Schedules listed are every two weeks, weekly and monthly, plus Backup Now, and a finished backup can be sent to Zoho WorkDrive or Google Drive.
Zoho says Ultimate users get four backups without payment, other paid editions get two free backups, and Free edition users must buy a one-time backup add-on or upgrade.
Data comes as CSV files in ZIP archives, with attachments in a separate ZIP. Zoho says the download link is active for a maximum of 7 days from backup creation.
A backup can take from minutes to hours depending on data size, and cannot be stopped once running or ready for download. The backup is stored in the same data center as the account.

What a backup does not cover, per Zoho

Zoho says emails configured with IMAP are not supported, documents and data obtained through integrations are excluded, and a contact's Account Name appears only as an Account ID in the backup file. Zoho's pages are inconsistent about whether activities and some email content are included, so check the live page rather than assuming.

Recovery options Zoho describes

Zoho's backup page does not describe a one-click restore. It lists these routes: investigate changes through the audit log, restore from the recycle bin within 60 days if it has not been emptied, re-import a single module's file (not advised when records have related data in other modules), import the full backup through data migration when related lists are affected or all data was erased, and contact Zoho support. Zoho says not to change the unique record IDs in the files because that impedes restoration.

A recovery habit worth having (practical advice)

This section is advice from experience, not vendor documentation.

Schedule a recurring backup and note who receives the completion email, since the download link expires.
Download and store each backup somewhere you control; do not rely on the link.
Restrict who can mass delete, and check the recycle bin as soon as someone reports missing records.
Before large imports or mass updates, take a backup first and test the change in a sandbox.
Confirm with Zoho support what your edition includes before an incident, not during one.

Sources

Zoho CRM data sharing rules: who can see which records

Skyfall — Thu, 05 Nov 2026 22:07:28 +0000

Roles and profiles decide what people can do; data sharing decides which records they can see. Mixing the two up is a common reason users report missing records or seeing everything. This post sets out what Zoho's help pages say about sharing rules and manual sharing.

The starting point: default organization permissions

Zoho's sharing-rules page says sharing rules extend access to users in other roles and groups, and that you cannot restrict the access set in the organization's default permissions by writing a sharing rule; rules can only add visibility. Zoho also says that if the organization default for a module is Public Read/Write or Public Read/Write/Delete, role hierarchy and sharing rules are not applied. Zoho's manual-sharing page says record-level sharing applies only if the module's default is Private or Public Read.

The pages do not list every default level or say which one is the starting default, so check Setup, Security Control, Data Sharing Settings in your own account.

Sharing rules, per Zoho

Users with the Manage Data Sharing permission can access the feature. Create a rule under Setup, Security Control, Data Sharing Settings, Sharing Rules tab, Create Sharing Rule.
A rule can be based on the record owner (records owned by users in selected roles, roles and subordinates, or groups) or based on criteria (field conditions combined with AND or OR).
You choose who receives access: roles, roles and subordinates, groups, or all users, at Read Only, Read/Write or Read/Write/Delete. A Superiors Allowed option extends access to superiors of the target role or group.
Rules apply to organization modules, not team modules.
Zoho says forecasts are always private, and that the organization-level sharing model is not yet implemented for Notes, Reports and Dashboards.
Rules cannot be edited while their execution is in progress, and a deactivated rule stops applying to newly added records until reactivated.
For very large modules (Zoho gives 4,000,000 or more records with 60% matching the criteria), existing records are not shared on save and Zoho says to contact support; new and updated matching records are still shared.

Manual record sharing, per Zoho

Record owners and their superiors with access, or users with the Share permission for the module, can share a record from its ellipsis menu. Zoho says this is available in Enterprise and Ultimate editions.
Access levels are Read Only, Read/Write and Full Access. Zoho says profile permissions override sharing: a user whose profile is read-only stays read-only even if Full Access is shared.
Zoho states caps for private sharing: 10 users, 5 roles and 5 groups directly; indirect sharing through related lists allows up to 12 users, 5 roles and 5 groups.
Records cannot be shared from the list view, only one at a time. Activities, linking-module records and team-module records cannot be shared this way, and some related items such as closed activities, products and campaigns are not shared.
Revoke Sharing removes direct sharing, but access granted indirectly through a parent record may remain.

Common pitfalls (practical advice)

This section is advice from experience, not vendor documentation.

If users see everything, check the module's default before touching rules: a Public Read/Write default bypasses rules per Zoho.
If users cannot see something, check in order: the default, the role hierarchy, then rules, then profile permissions.
Prefer a few criteria-based rules with clear names over many one-off manual shares, which are hard to audit.
Document who should see what before changing defaults, and test with a user in the target role in a sandbox first.
Check feature availability for your edition before designing around rules.

Sources

Zoho CRM CommandCenter: customer journeys vs Blueprint

Skyfall — Thu, 05 Nov 2026 21:46:37 +0000

CommandCenter is Zoho's journey tool, and it is easy to over-build with it when a Blueprint or workflow would do. This post sets out what Zoho's help pages say about it.

What CommandCenter is

Zoho describes CommandCenter as a journey management suite in Zoho CRM with three parts: Path Finder, which helps discover the journeys prospects and customers take; Journey Builder, which builds contextual journeys; and Analytics, which exposes the journeys taken in your organization. Access requires the CommandCenter permission under Automation.

Zoho's page lists Professional, Enterprise, Ultimate, CRMPlus, ServicePlus and Zoho One bundles, and points to its release notes for current feature availability and limits. Check feature availability for your edition.

Setting up a journey, per Zoho

Go to Setup, Experience Center, CommandCenter, Journey Builder, click Create Journey, enter a name and description, and click Proceed.
The builder starts with a Start stage. Add stages with Create Stage; goals are optional and are set by clicking the Start stage.
Connect stages with transitions that hold signals: record actions, user actions such as email, call or web form, integration signals from Zoho apps, and custom signals.
Open a stage's Actions tab and create an action group, which can be instant, scheduled or recurring. Zoho lists action types including field updates, functions, webhooks, tasks and email notifications.
Zoho says identifiers are mandatory to publish a journey; Manage Identifier sets them for all transitions at once.

Caveats Zoho documents

Zoho says you cannot uncheck the run-for-specific-records option once selected; to change it, delete the action group and reconfigure.
Ending a journey at an end stage does not prevent a record entering another journey it qualifies for.
Zoho's help page gives conflicting figures for identifiers per transition (ten in one note, five in another), so check the live page.
Zoho's pages reviewed do not state limits on the number of journeys, stages or records, or what editing a published journey does.
If Journey Builder, workflows and Cadences are configured for the same touchpoint, Zoho warns customers may receive the same email several times.

CommandCenter vs Blueprint, per Zoho

Zoho's comparison page says both are built on a finite state machine with states, transitions and actions. It describes Blueprint as a business process tool to promote compliance, for internal teams, with states from picklist values and transitions that depend on completing required actions. Journey Builder it describes as a tool to optimize the customer journey across touchpoints, for customers, with free-form states and transitions driven by signals or events. Blueprint is built for a single module, while Journey Builder can span modules. For simple email, task and call follow-up, Zoho suggests Cadence Studio, saying Journey Builder can do this but it may be laborious.

Deciding what you need (practical advice)

This section is advice from experience, not vendor documentation.

If you need to force a team through required steps on a record, start with a Blueprint.
If you need one condition to trigger one action, a workflow rule is usually enough.
Consider CommandCenter only when a process has many stages, reacts to events across channels and modules, and you can draw it as a flowchart.
Draw the journey on paper first and name the signal for every transition.
Never configure the same action in two automation tools for the same touchpoint.

Sources

Zoho CRM sales forecasts: setup and why they miss

Skyfall — Thu, 05 Nov 2026 21:36:04 +0000

Disclosure: I work at Skyfall Labs, an official Zoho Partner, so I have a commercial interest. The facts below are from Zoho's own help page, linked at the end; advice is labelled as advice. Originally published on skyfallhq.net.

Forecasts that nobody trusts usually come from configuration choices made early and rarely revisited. This post sets out what Zoho's help page says about forecast configuration, categories, targets and periods.

Who configures forecasts

Zoho says forecast configuration can be set only by CRM administrators, and it applies across the organization, including across teamspaces. The configuration covers the forecast model (top-down is the default, bottom-up is the alternative), the hierarchy used (role or reporting, or territory), and the fields used for estimation: Deal Revenue, Deal Quantity, or a system-defined count of deals. Zoho recommends selecting both revenue and quantity. The fiscal year is taken from Company Settings. Zoho's page does not state which editions include forecasts; check feature availability for your edition.

Forecast categories

Per Zoho, the five system categories are Pipeline, Best case, Committed, Closed and Omitted, and you can add two custom categories for the Open stage. Categories are set through stage probability mapping. System categories such as Pipeline, Best case and Committed can be renamed but not deleted, and once a deal is closed (won or lost) its forecast category is locked.

Managers, targets and periods

Reporting and territory managers are automatically forecast managers. In the role hierarchy, forecast managers are assigned manually, and Zoho says only one forecast manager can exist for a particular role.
Zoho's page uses the word target rather than quota. Top-down splits a company target down the hierarchy; bottom-up sums individual targets that users submit for approval.
A forecast period is quarterly or monthly, and can be current, future or completed. Custom fiscal years offer quarterly and periodly options.
A forecast can cover all deals or selected deals defined by criteria. Continuous forecasts can be created from an existing forecast, and targets can be populated from Zia's suggestion, the previous target or the previous achievement.

Stated limits and changes with lasting effects

Zoho says forecasts are currently supported for two previous years and one future year.
Zoho says that editing the forecast configuration deletes current and future forecasts based on the old configuration, while completed forecasts are archived.
Zoho says changing the organization's fiscal year deletes all existing and archived forecasts.
Completed forecast targets cannot be edited.
Zoho says admins can lock target submission, and that a maximum of five notification emails can be sent to a user.

Why forecasts drift from reality (practical advice)

This section is advice from experience, not vendor documentation. Zoho's page does not discuss forecast accuracy.

Forecast categories follow stage probability mapping, so stages that no longer match how deals really progress will produce misleading categories.
Deals with stale close dates, missing amounts or no owner distort every roll-up; fix the data before blaming the forecast.
Decide the model, hierarchy and fiscal year before creating forecasts, because changing configuration deletes forecasts.
Agree what counts as Committed with the sales team, in writing.
Review the forecast against closed results each period and adjust stage mapping, not just the numbers.

Sources

Zoho Help: Setting up forecast configuration and creating forecasts

Zoho CRM custom modules: when to build one (and when not)

Skyfall — Thu, 05 Nov 2026 21:16:14 +0000

A common sign of a CRM that has grown messy is a pile of custom modules that overlap with the standard ones. Zoho's help pages explain what custom modules are and what they cost you in flexibility later. This post sets that out.

What Zoho says a custom module is for

Per Zoho, standard modules come with predefined fields and layouts for Sales, Marketing, Customer Support and Inventory, and most of them can still be edited. Custom modules are for cases where the standard, predefined modules do not always meet your requirements. Zoho's examples are a school using Students, Teachers and Parents, and a hospital using Doctors, Patients and Nurses. Zoho's page does not give a formal checklist for choosing between a custom and a standard module.

Zoho also distinguishes custom modules from Custom Apps, which are built with Zoho Creator and placed as custom tabs.

Who can create one and how

Users with the Module Customization permission in their profile can access the feature; Zoho says Admin profiles have it by default.
Go to Setup, Customization, Modules and Fields, and under the Modules tab click Create New Module.
Choose organization modules (or team modules, if that fits), enter the singular and plural names, and save. Names must be unique.
Add the teamspaces where the module should appear, select the profiles that get module permission, and save.

Stated limits

Zoho states that module counts are combined for custom and team modules: Standard 10, Professional 25, Enterprise 200 and Ultimate 500. It says there are no longer user-based restrictions on adding custom modules, and its page does not state a module limit for the Free edition. Custom fields are not available in the Free edition, field limits vary by edition, and a Custom Fields Left counter shows how many you can still create. Formula fields are not available in the Standard edition. Check feature availability for your edition on Zoho's page before designing around any of these.

What you can change later, and what you cannot

You can rename a module, add or remove fields, rearrange sections and fields, and change profile permissions. Removed fields move to an Unused Fields section.
Zoho says the field properties of default fields are not editable, though the default field name label can be edited.
Zoho says that once you delete a custom module you cannot restore data from it. Deletion permanently removes its records, custom fields, workflows, reports, dashboard components, email templates and other associated items, and Zoho says to make sure the module is not linked to another module first.
If you downgrade to an edition that does not support a custom module, Zoho says its data is hidden and returns when you upgrade.

What custom modules can do

Per Zoho, custom modules support field-level permissions, imports, backups, mass emails, macros, workflow rules, relationships with standard modules and autoresponders. Layouts are configured with a WYSIWYG Module Editor, with Quick Create forms and a Detail View per layout, and you can preview a layout as a specific profile.

Choosing between custom and standard (practical advice)

This section is advice from experience, not vendor documentation.

Ask first whether the thing you want to track is really a person, a company or a sales opportunity. If it is, a standard module with extra fields, a layout or a picklist value may be enough.
Build a custom module when you track a distinct kind of record with its own fields and its own relationships, such as a policy, a property or a project.
Write down how the new module relates to Accounts, Contacts and Deals before creating it, since deletion cannot be undone.
Check the module count and field limits for your edition so you do not hit a cap mid-project.
Test in a sandbox or on a small data set before importing real records.

Sources

Zoho Help: Creating custom modules

Zoho CRM customer portal: setup, permissions and pitfalls

Skyfall — Thu, 05 Nov 2026 20:46:20 +0000

Disclosure: I work at Skyfall Labs, an official Zoho Partner, so I have a commercial interest. The facts below are from Zoho's own help page and portals page, linked at the end; advice is labelled as advice. Originally published on skyfallhq.net.

A customer portal lets customers, partners or vendors see and work with their own CRM data without a licence as a CRM user. It is also easy to configure in a way that cannot be reversed. This post sets out what Zoho's help pages say.

What a portal is

Per Zoho, portals let administrators give contacts, vendors, partners and users of custom modules access to CRM, where they can view, create, edit and add notes to the records they have access to, plus view associated products, invoices and notes. Zoho's portals page describes self-service portals for customers, partners or vendors, where you decide what each can see and do, invite them, and they set up credentials and log in.

Setting one up, per Zoho

Users with the Manage Portal Profile permission can create a portal and invite customers.
Go to Setup, Channels, Portals, click Get Started Now, and confirm or edit the portal name (the default is the company name), then click Configure Now.
Create a user group: name, primary module, related modules, invitation preference and related field; then configure the portal module and field permissions and click Finish.
Preview from Setup, Channels, Portals, Preview, choosing a group.

User groups and editions

Zoho says up to five user groups can be configured and the first must be a customer group. Zoho's page says a number of portal users across all groups are included and that additional portal user licences are charged beyond that; check Zoho's page for the current allowance and licence terms. For trials, Zoho says Enterprise and Ultimate trial users get a 30-day trial with a Contacts group capped at 10 users and no new groups. Zoho's page does not otherwise state which CRM editions include portals; check feature availability for your edition.

Permissions and fields

Record permissions are Create, Edit, View, Delete and Edit (Shared); Edit (Shared) lets portal users edit records CRM users added.
Field permissions are set per module, not per layout, and subform permissions are set separately from the parent module.
Fields can be marked Read Only; mandatory CRM fields stay mandatory in the portal.
Portal users cannot be record owners; records they create are owned by the inviting CRM user.
Zoho says products must be shared for portal users to link products to inventory records.

Invitations

Zoho says invitations go by email or phone, with phone supported only for companies registered in India. Email invitations expire after 7 days. Invitations can be sent one at a time from a record, in bulk from the Users tab, or automatically through Auto-Invite. Zoho lists reasons an invitation can fail, including pending approval, no GDPR consent, a license limit reached, no module or record permission, and a user already in a group.

What cannot be undone

Zoho says that once a portal is configured it cannot be deleted.
The invitation preference cannot be changed after users are added or a portal form is created; Zoho says to contact support.
The Client Portal group cannot be deleted, only turned off and on.
A group with users can be deleted only after transferring them to another group for the same module.

Before you launch (practical advice)

This section is advice from experience, not vendor documentation.

Decide what a customer actually needs to see or do, and start with the smallest set of modules and fields.
Check the portal user allowance and licence terms for your edition before inviting a large list.
Test with a handful of real invitations and the Preview before bulk invites.
Review field and record permissions as a customer would, since a portal exposes CRM data outside your team.
Because configuration is hard to reverse, write the design down and agree it before clicking Configure Now.

Sources

Zoho CRM mass email limits and deliverability

Skyfall — Thu, 05 Nov 2026 20:36:07 +0000

Teams often find that a mass email stops short, or that CRM emails land in spam, and conclude Zoho is unreliable. Zoho's help pages explain the daily limits and the domain authentication it expects. This post sets those out.

Mass email limits, per Zoho

Zoho's Email Limits page gives daily mass email limits per organization: Standard 250, Professional 500, Enterprise 1,000 and Ultimate 2,000. Autoresponders, active email schedulers, macros and mass emails all count toward that total. A day runs from midnight to 11:59 PM in the organization's time zone. Zoho says the limit can be raised to 10,000 per day per organization for an additional cost by contacting the sales address listed on the page.

One-to-one email limits

Individual email limits are separate and based on confirmed, active users. Per Zoho, free and trial editions allow 50 emails per confirmed user per day, with To and CC recipients both counting, and paid editions allow 300 per confirmed user per day, which can be shared across the organization. Zoho says mass emails and emails sent from the organization email address set up in Zoho CRM are sent from Zoho's servers.

Authenticating your sending domain

Zoho's help describes email authentication for sending from Zoho CRM with your own domain as involving three standards: domain verification, DKIM and SPF. It describes DKIM as verifying the authenticity of the sender and protecting the message from alteration in transit, and SPF as letting domain owners specify which servers may send on their behalf. After completing authentication in Zoho CRM, you add the automatically generated SPF and DKIM records at your domain manager.

DNS points Zoho's page raises

Both records are TXT records; the values and the DKIM host name come from the SPF/DKIM Setup screen in your CRM account.
If you already have an SPF record, Zoho says not to add a second one; edit the existing record to add the Zoho include.
Zoho says multiple SPF records can break the check and may send emails to spam.
The SPF include value depends on your Zoho region (for example US, EU, IN, AU, CN, JP); use the one on Zoho's page for your data centre.
Some DNS providers append your domain automatically to record names; Zoho says to end the name with a dot to prevent it.
Zoho's page does not state edition requirements or how long DNS changes take to take effect.

Pitfalls worth checking (practical advice)

This section is advice from experience, not vendor documentation.

Count every source against the daily cap. Autoresponders and macros share it with mass emails, so a campaign can be cut short by other automation.
Authenticate the domain before the first campaign, not after complaints about spam folders.
Check your DNS for an existing SPF record before adding anything.
Plan large sends around the cap, or check with Zoho whether a separate Zoho product suits very large volumes.
Send test messages to several mailbox providers and read the results before a full send.

Sources

Zoho CRM web forms: lead capture setup and fixes

Skyfall — Thu, 05 Nov 2026 20:16:06 +0000

A web form that quietly drops leads, or floods the CRM with spam, is one of the most common reasons teams feel Zoho is not working for them. This post sets out what Zoho's help pages say about web forms, assignment, spam and troubleshooting.

What web forms support

Per Zoho, web forms are supported for Leads, Contacts, Cases and any other custom modules in your account. Zoho says to test the form before publishing it on your website, and that changes take effect only once you host the newly generated code on your site. Zoho adds that removing or deleting a web form does not delete the data it already captured.

Zoho does not state in these pages which editions include web forms or specific features of them; check feature availability for your edition.

Spam: what Zoho recommends

Zoho's FAQ recommends three defences together: enabling CAPTCHA, creating a record approval process, and creating a validation rule. Zoho says that even if a bot bypasses CAPTCHA, it cannot get past the validation rule in CRM, and that spam records are moved to Invalid entries on the Leads Approval page.

Approval of captured leads

A form can require manual approval. If it does, Zoho says the leads from the form appear under the Leads tab only once a user with the Approve Records permission approves them. To check whether a form has this on, go to Setup, Channels, Webforms, open the form, click Next Step and look for Request for Approval on the Form Details page. Pending records are approved from the module's tools menu.

Who gets the lead

Zoho's FAQ says that by default incoming records are assigned to the administrator, and that you can create an assignment rule to assign records to specific users or by round robin. The leads-management FAQ likewise points to an assignment rule with the round robin option to distribute web form leads equally among salespeople.

Duplicates

Zoho's suggestion for stopping duplicate leads is to make the Email field unique: Setup, Customization, Modules and Fields, select Leads, open the Email field's settings, choose Do not allow duplicate values, and save the layout. Existing duplicates can be merged.

Why leads do not appear: Zoho's checklist

The form's HTML uses HTTP; Zoho says to change it to HTTPS.
The default Zoho hidden fields were removed; Zoho says the form then will not work.
The domain name in the form settings does not match the URL where the form is hosted; Zoho says the information is then not captured, and that entering an asterisk in square brackets allows capture from other or multiple domains.
The form is not active.
Records are waiting in the approval queue.
You do not have permission to view the lead records.
The hosting site converts some special characters.
Several web forms on one page: Zoho says leads captured this way cannot be viewed.
If visitors land on the wrong page after submitting, Zoho says to check the Landing Page URL under Setup, Channels, Webforms.

Setting up forms that work (practical advice)

This section is advice from experience, not vendor documentation.

Decide before building who owns each lead source and set the assignment rule first, so nothing sits with the administrator by default.
Submit a test entry from the live page, not just the preview, and confirm it lands where you expect.
Turn on spam defences before the form goes public, not after the first spam wave.
Re-test after any website redesign or hosting change, since the form code lives on your site.
Put a named person in charge of the approval queue if you use one, otherwise real leads wait unseen.