Deleting a user group in Zoho CRM is not directly documented in the sources available to our team at this time — however, the closest supported path involves managing group membership and user removal through Zoho's admin interfaces and, where applicable, the Zoho Mail Groups API.
Why this matters
User groups in Zoho CRM are used to assign records, automate workflows, and control data visibility across teams. When a group is no longer needed — for example, after a team restructure — leaving it in place can cause confusion in assignment rules and reporting. Knowing the correct deletion path prevents orphaned configurations and keeps your CRM tidy. As an independent expert support resource (not official Zoho support), Beam Help recommends verifying any admin action in a sandbox or with a test group first.
Step-by-step
Step 1. Before removing any group, audit which records, workflows, or assignment rules reference it. If the group is actively used in Zoho services, removing it or its members may affect related functionalities. [4]
Step 2. If your groups are managed at the Zoho One directory level (i.e., synced from a Directory Store or an AD Sync tool), you must initiate the deletion from the source system rather than from within Zoho CRM directly. Attempting to delete from within Zoho without updating the source may cause the deletion to be reverted. [1]
Step 3. When a user who owns or administers the group is being removed from the organisation, Zoho One's structured deletion workflow automatically removes that user from all groups and departments as part of the guided process. Walk through each step of that workflow — including transferring application ownership, reassigning department ownership, and updating the reporting hierarchy — before the user is fully removed. [4]
Step 4. If you are working with Zoho Mail groups (which can be linked to CRM team inboxes or shared mailboxes), the Groups API supports a dedicated delete operation. The endpoint follows the pattern DELETE /api/organization/{zoid}/groups/{zgid} or a bulk variant at DELETE /api/organization/{zoid}/groups. Use this when you need to programmatically remove a mail-linked group rather than doing so through the UI. [5]
Step 5. For Zoho Analytics workspaces that mirror CRM data and use shared groups, the DELETEGROUP action can be called via a POST request to https://<hostname>:<webclientport>/api/<emailaddress>/<Workspacename>, passing the group names in a CONFIG parameter. A successful response returns a message confirming the groups were deleted. [7]
Step 6. Once the group has been removed (or its members cleared), verify in the Zoho One admin panel that the user's license status reflects the change. A user's license remains occupied until they are completely removed from the system, so confirm the licence count has updated as expected after the group cleanup is finalised. [4]
Common pitfalls
- Synced groups revert after deletion. If your CRM groups are tied to a Directory Store or AD Sync integration, deleting them inside Zoho without first removing them at the source will cause the deletion to be reversed on the next sync cycle. Always start at the directory source. [1]
- Active service dependencies. Groups that are actively referenced in Zoho services (workflows, assignment rules, shared inboxes) may cause disruption if removed without first reassigning those dependencies. Review all active references before proceeding. [4]
- License not released immediately. Removing a user from a group does not instantly free their licence. The licence remains occupied until the user is fully removed from the system through the complete deletion workflow. [4]
What to check
- Confirm the group no longer appears in any active workflow, assignment rule, or data-sharing configuration inside Zoho CRM.
- Verify in the Zoho One admin console that the user (if deleted) has been removed from all groups and departments, and that the licence count has updated. [4]
- If the group was mail-linked, confirm via the Zoho Mail Groups API (
GET /api/organization/{zoid}/groups/{zgid}) that the group record no longer exists. [5]