Zoho CRM User Management Guide

• Model type: hybrid
• Description: Zoho CRM uses a two-layer hybrid model. Profiles control feature-level permissions (which modules and actions a user can access). Roles define data visibility through a hierarchical structure (users in higher roles can see records owned by subordinate roles). Data Sharing Rules can further expand record visibility across roles. Field-level security is available to restrict individual field access within modules.
• Custom roles: Yes
• Custom roles plan: Available on Standard plan and above
• Granularity: Module-level and field-level permissions via Profiles; record-level visibility via Role hierarchy and Data Sharing Rules; territory-based access available on Enterprise and above.

1. Log in as an Administrator or user with 'Manage Users' profile permission.
2. Navigate to Setup > Users and Control > Users.
3. Click '+ New User' (or 'Invite Users').
4. Enter the user's First Name, Last Name, and Email Address.
5. Select a Role from the role hierarchy.
6. Select a Profile to define feature permissions.
7. Optionally assign the user to a Territory (Enterprise and above).
8. Click 'Save' to send an invitation email to the user.
9. The user must accept the invitation and set a password before their account is active.

Required fields: First Name, Last Name, Email Address, Role, Profile

Watch out for:

• The invited user must accept the email invitation before they can log in; the seat is consumed once the invitation is sent, not when accepted.
• Email address must be unique across Zoho accounts; if the user already has a Zoho account under a different organization, they will be prompted to switch.
• Adding a user beyond the purchased seat count will prompt an upsell to purchase additional licenses before the invitation can be sent.
• Users added via invitation are active immediately upon acceptance; there is no draft/pending state that holds a seat without consuming it.

• Can delete users: Yes
• Delete/deactivate behavior: This app exposes delete operations in its API documentation, but the admin-console path may present removal as deactivation, archiving, or deletion depending on tenant configuration. Confirm whether the UI action is reversible before treating removal as recoverable.

1. Navigate to Setup > Users and Control > Users.
2. Locate the user in the Active Users list.
3. Click the user's name to open their profile, or use the action menu (three-dot icon) next to the user.
4. Select 'Deactivate'.
5. Confirm the deactivation in the dialog prompt.
6. The user is moved to the Inactive Users list and can no longer log in.

Watch out for:

• A user cannot be deleted until all records owned by that user are transferred to another active user; the system enforces this before allowing deletion.
• The Super Admin (account owner) cannot be deactivated or deleted without first transferring account ownership.
• Deactivated users still appear in historical activity logs and audit trails, preserving data integrity.
• If a deactivated user is the only member of a role, that role remains in the hierarchy but has no active members; this can affect data sharing rule calculations.

• Where to check usage: Setup > Users and Control > Users - the Users page displays total active users vs. purchased seats. Subscription details are also visible under Setup > Subscription.
• How to identify unused seats: Navigate to Setup > Users and Control > Users and filter by 'Active Users'. Review the 'Last Login' column to identify users who have not logged in recently. No built-in 'unused seat' report exists; admins must manually review last-login timestamps.
• Billing notes: Zoho CRM is billed per user per month. Seats are consumed when a user invitation is sent (not when accepted). Deactivating a user frees the seat for reassignment. Annual billing requires purchasing a minimum number of seats upfront; mid-cycle seat additions are prorated. Seat reductions on annual plans typically take effect at the next renewal cycle.

Seats are consumed the moment an invitation is sent, not when the user accepts it. That means a delayed onboarding or a bounced invite email still costs a license. Identifying idle users requires manually reviewing the Last Login column under Active Users - there is no built-in unused-seat report or automated alert.

On annual plans, seat reductions typically take effect only at renewal, so over-provisioning mid-cycle has a real cost that doesn't self-correct quickly.

Community evidence is not specific enough to quote or summarize yet for this app.

Deactivation is the safer default for offboarding: it blocks login, preserves all owned records, and keeps the user visible in audit trails. Deletion is available but requires a full record-transfer step first and is irreversible.

The Super Admin designation cannot be transferred through normal user settings - it belongs to the original account owner and requires a separate ownership-transfer process. Light CRM User seats offer a reduced-access option, but seat availability and limits vary by plan, so verify current entitlements before provisioning them at scale.

Bottom line

Zoho CRM's manual user management is functional but requires deliberate setup at every step. Every app that relies on CRM data visibility is only as accurate as the Profile and Role combination assigned to each user.

The absence of automated idle-seat detection and the mandatory record-transfer step before deletion are the two operational gaps most likely to create ongoing admin overhead.

Teams managing more than a handful of users should establish a documented offboarding checklist and a recurring Last Login audit cadence to keep seat usage clean.