When a Zia Agent is deployed as a Digital Employee, it receives a dedicated identity within Zoho CRM — a named profile that holds ownership of records it creates and manages, separate from any human user account. Understanding exactly what a Digital Employee can and cannot do is essential for designing automation correctly and setting appropriate expectations with your team.

What a Digital Employee Is

A Digital Employee is a CRM identity assigned exclusively to a Zia Agent — it is not a standard user licence and is not billed as one. It appears in Setup › Users and Control › Users alongside your human team members, but it operates under fundamentally different rules. Its primary purpose is to give the agent a clear, auditable owner identity for every record and action it touches, so that AI-driven changes are always distinguishable from human-driven ones in the activity history.

Supported Functions

Digital Employees have broad operational capability across the core CRM workflows:

• Record creation — both standard record creation and Quick Create are supported, with the Digital Employee set as the record owner at the point of creation.
• Owner change workflows — the Digital Employee can be the target of ownership transitions triggered by automation, providing a clean handover point from agent to human or between agents.
• Mass transfer — records owned by the Digital Employee can be transferred in bulk, either to a human user or to another agent identity.
• Import as default owner — when records are imported into CRM, the Digital Employee can be set as the default owner for imported rows.
• Lead convert assignments — the Digital Employee can be assigned during the lead conversion process, taking ownership of resulting contacts, accounts, or deals.
• Custom views — views can be filtered by the Digital Employee using the Record Owner filter, making it easy for managers to see all records the agent is currently handling.
• Reports and dashboards — the Digital Employee appears as an owner column and filter option in reports, allowing performance analysis of agent-managed records alongside human-managed ones.
• Smart filters — smart filter options within relevant modules recognise the Digital Employee as a valid owner for segmentation.
• Mass operations — mass convert, mass transfer, mass update, and mass delete are all available when the Digital Employee is the relevant record owner.

Unsupported Functions

There are specific areas where a Digital Employee cannot participate, and these constraints are important to account for when designing your automation architecture:

• Users Lookup fields — any field in CRM configured as a Users Lookup will not recognise the Digital Employee as a selectable value. These fields are restricted to human user accounts.
• Manual automation rule assignment — you cannot manually assign an automation rule to direct records to a Digital Employee. The agent acquires ownership only through its own actions.
• Workflow rule record owner assignment — workflow rules that update the record owner field cannot be configured to target a Digital Employee as the destination owner.
• Assignment rule manual configuration — assignment rules cannot be manually configured to route records to the Digital Employee.
• Approval process ownership — the Digital Employee cannot be set as an approver or owner within an approval process configuration.
• Deletion from the Users page — a Digital Employee cannot be deleted from Setup › Users and Control › Users. Removal must be performed from the Zia Agents configuration area.
• Role reassignment from the Users page — similarly, role changes for a Digital Employee must be made through the Zia Agents interface, not the standard Users page.

Audit Clarity

One of the most operationally valuable aspects of the Digital Employee model is the separation it creates in activity history. Because the agent operates under a distinct CRM identity, every record it creates, updates, or transfers is logged under that identity — not under a generic system account or a shared user. This means that when reviewing a lead's history, a manager can see precisely which actions were taken by a human representative and which were performed by the AI agent, without ambiguity.

This clarity is particularly important for organisations operating under data governance or compliance requirements, where accountability for CRM actions needs to be demonstrable and auditable.

Administration

The Digital Employee appears in Setup › Users and Control › Users and is visible in the user list alongside human accounts. However, administrative actions — including role changes and deletion — must always be performed through Setup › General › Agents, not from the Users page. Attempting to manage the Digital Employee from the Users page will not surface the required controls for these operations.