Zoho for trade shows: separate organizer and exhibitor processes

A trade show organizer and an exhibiting company may share an event calendar, but they do not manage the same process. The organizer follows stand sales and delivery, while the exhibitor tracks stand conversations. A program code in Zoho CRM does not merge the ledgers. Separation depends on ownership, sharing rules, field permissions, and personal-field marking.

This design extends beyond layouts. Decision authority, record visibility, report behavior, and permitted data transfer channels require separate treatment. Technical controls do not answer questions between two legal entities. Ticketing, a microsite, or check-in creates a different product boundary from guest management. Defining distinctions keeps event operations from combining records that serve different purposes.

Organizer and exhibitor ledgers measure different work

The organizer's ledger tracks the buying organization, floor area, corner stand position, option period, contract review, and delivery authority. The exhibitor's ledger focuses on a stand conversation, its internal owner, and closing reason. The event produces different decisions, responsibilities, and commercial outcomes for each party, so record purposes begin separately.

A common program code does not create a shared lifecycle. The Campaigns module is available in every edition and holds trade show guest statuses. Up to 50 values, such as Invited, Attended, or Not Attended, may be defined. This reference does not turn exhibitor conversations into organizer stand-sale records.

A user field identifies the decision owner; a lookup pointing to another module's record serves a different purpose. A shared calendar or campaign connection does not create shared ownership or access. Locking stand inventory during a transaction remains a separate design topic outside this process separation here.

Keep decision authority in a user field

When authority to extend a corner stand option, approve a floor-area discount, or accept a hall plan change belongs to one person, keep it in a user field. Zoho CRM has no field type that selects a role or group. A lookup for another module cannot replace a user field.

If a role distinction is needed, a picklist can sit beside the user field. Its values do not map automatically to CRM roles and require manual maintenance. A multi-select picklist for consulted groups likewise does not select CRM groups. Otherwise, a hall-approval label can be mistaken for system authority.

Each module allows up to five single-user fields and one multi-user field for at most ten users. These fields are unavailable in Tasks, Calls, and Meetings. Decision-authority fields require custom fields, so Free cannot support this setup. Plan quota across stand sales, contract review, and delivery responsibilities.

Access follows the record owner

Record visibility begins with ownership. A user can see a record when they own it, sit above the owner in the role hierarchy, cover its territory, or receive access through a sharing rule. Zoho has no ownerless shared-pool object. For queues, a dedicated user owns records until transfer to actual owners.

To give an outside user access to stand contracts or exhibitor conversations, use a user field identifying them. Its properties grant read-only, read-write, or full access. Alternatives include record-level sharing, data sharing rules for roles or groups, and territory management. Without Superiors Allowed, a manager does not see data shared with a subordinate.

Hiding a field from another operating model, or making it read-only, requires field-level permission. Available in Professional and above, it works by profile across every module layout. Standard lacks this distinction, although record history shows changes. Administrators need a separate profile to remain outside restriction. Territory management starts with Enterprise.

Test the boundary in reports and exports

A report is not another privacy layer. Users see records accessible in the primary module. Adding parent or child module fields may expose those fields and records without access to related records. Keep a module carrying a confidential field out of the report. Sharing operates by report folder, while admins see every report regardless of sharing.

On the show's second day, an organizer sees a note recorded at an exhibitor's stand. The note is not hidden, and its module is a parent module in the report. This shows why record screens alone cannot validate access. Test record creation, field changes, report viewing, and export with a low-permission profile.

Dashboard sharing does not override field permissions; components using restricted fields stay invisible. CRM permissions do not apply to embedded dashboards, where allowed domains are the only access check. Personal field marking restricts exports, API access, Zoho apps, and third-party transfers. Reports display 2,000 records; formatted exports 2,000 rows and detailed exports 50,000.

Technical separation does not create legal separation

Personal fields are marked Normal or Sensitive, up to 30 per module. Auto Number, Formula, User, and Lookup fields cannot be marked; neither can First Name or Last Name. The technical effect restricts movement through four transfer channels. Enabling an integration transfers personal data to a third party.

The compliance framework covers only Leads, Contacts, Vendors, and custom modules, excluding Deals and Accounts. Data requiring consent records connects to the contact. Enabling a product setting does not establish legal compliance. Zoho does not present these settings as legal advice, so technical effects and regulatory assessment remain separate.

For each activity, determine which entity decides processing purpose and method and which processes the data. A data controller is a status, not a CRM user or role. Contract requirements, each party's notice duties, and the basis for every interparty disclosure require separate assessment. The organization's legal team owns classification; access controls cannot resolve it.

Define the Backstage boundary before ticketing

When a guest list and one channel suffice, the Campaigns module available in every edition supports it. Ticket sales, a microsite, and check-in move the boundary to Backstage. The integration adds a Backstage layout to Campaigns and consumes one layout allowance. Backstage events appear as CRM campaigns, connected one-to-one with the CRM organization.

Attendees and guests can be pushed into CRM as Leads or Contacts through Push Settings. Purchase, Check-in, and Cancel ticket events can signal scoring rules. Backstage details are edited only there. CRM badge-printing mechanics are not documented within the boundary, so no entry-operation capability should be assumed.

Free cannot support this decision-field setup because custom fields are unavailable. Field-level permissions begin with Professional, and territory management with Enterprise. Campaigns is available in all editions. Assignment rules require the Assignment Rules & Threshold profile permission, not an edition. No edition threshold is stated for compliance settings, so none is inferred.

Assignment rules do not run on show-floor entries

Assignment rules run only on records from imports, web forms, or the API; they do not trigger for manual stand entries. The owner must be selected during entry. Each rule entry accepts up to 25 criteria. Rules choose the owner, optionally create a follow-up task, and send unassigned records to the default user.

A stand representative manually creates a phone-request record. The assignment rule never runs, so it remains with its creator and an unexpected name appears on the evening list. Assignment Threshold only warns during manual creation, manual editing, mass transfer, and imports. It neither stops the record nor changes its owner.

The default user is the import initiator, API token owner, or web-form rule creator. If that user is deleted or inactive, the record goes to the super administrator. A wrong default owner can cross the operating-model boundary. The audit log tracks changes and transfers, but not record views, limiting exposure investigations.

Zoho CRM