Data security

Control who sees whatin your customer data

Role-based, department-based and per-Zalo-account permissions, together with phone number masking and an audit log, help businesses protect customer data from being copied outside.

Book a demo See how permissions work

Three roles (Owner/Admin/Member) with different permissions, plus department-based RBAC
Mask customer phone numbers and log every action for audit

The three roles Owner, Admin, Member in ZCRM

Data security

Explore the features

From role-based permissions to phone number masking and an audit log, every protection layer is ready to enable in ZCRM.

User permission screen in ZCRM — User permissions
Three roles: Owner, Admin, Member, each with different view, chat and admin rights.

Customer phone number masking feature — Phone number masking
Mask customer phone numbers so employees can't copy them out when it isn't necessary.

Phone numbers hidden in a customer list — Hidden numbers in customer lists
Once enabled, phone numbers are hidden right in the customer list, not just in the detailed profile.

Phone numbers hidden in the friend list — Hidden numbers in contacts
Phone numbers are also hidden in the Zalo friend list to protect synced data.

Department-based permission map — Department-based RBAC
Configure custom permission groups more granular than the 3 default roles for multi-department businesses.

Audit log in ZCRM — Audit log
Trace who did what in the system, useful for investigating incidents when needed.

Several protection layers around one customer

From account roles down to a specific Zalo account, each permission layer limits access to exactly what's needed.

Owner/Admin/Member roles
Department-based RBAC
Custom permission groups
Per-Zalo-account permissions
Work scope
Customer phone masking
Audit log
Two-factor login on the app

Role-based permissions

Three roles, three different permission levels

Owner, Admin and Member each have different view, chat and admin rights, letting owners control who can view, who can chat, and who can administer each Zalo account.

Multi-department businesses use department-based RBAC and custom permission groups for finer control than the 3 default roles.

3 roles Owner / Admin / Member with different rights
Department-based RBAC & custom permission groups
Access permissions per individual Zalo account

Phone number masking

Protect customer phone numbers from being copied outside

Turning on phone number masking hides numbers in the detailed profile, the customer list and the Zalo friend list, not just in one place.

This protects customer data when an employee leaves the team, without stopping sales from chatting normally with customers.

Masks the phone number in the detailed customer profile
Hides numbers in customer lists and the friend list
Protects data when an employee leaves the team

Audit log

Trace who did what in the system

The audit log records user actions across the system, supporting internal compliance and incident investigation.

On the mobile app, two-factor login adds another layer of protection for the company account when used on an employee's personal phone.

Audit log traces user actions
Supports internal compliance and incident investigation
Two-factor login protects the account on the mobile app

Role- and department-based permissions

Three default roles plus department-based RBAC for multi-team businesses.

Customer phone masking

Hides phone numbers in profiles, customer lists and the friend list.

A complete audit log

Traces every action in the system for compliance and investigation.

Explore other solutions

See how ZCRM protects your customer data

Book a demo so the ZCRM team can walk you through configuring permissions, masking phone numbers and reading the audit log.

Book a demo