This article Download.vn will guide you to turn off the "Just accessed" notification under your chat account name on Zalo . This will limit other people from bothering you when you are too busy with work to talk.
Video tutorial to turn off the "Just accessed" notification on Zalo
Instructions to turn off the "Just accessed" notification on Zalo
Step 1: First we will open the Zalo application on our phone, then click the Add icon in the lower right corner of the screen.
Step 2: Then, click the Settings icon in the lower right corner of the screen.
Step 3: In the Settings section of the Zalo application, tap Privacy .
Step 4: Next, turn the switch in the Show access status section to the right.
Step 5: At this point, if we try to access any friend's conversation, we will see the "Just accessed" message disappear.
In addition, you can also refer to some articles about other Zalo tricks such as:
Wishing you success!
Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.
Compare YaST and cryptsetup for a new encrypted SLES data volume, choose LUKS1 or LUKS2, and verify unlock and mount behavior safely.
Create, refine, and verify a least-privilege AppArmor profile on SLES 15 SP7, with a clear note on SLES 16’s SELinux default.
Set up RMT on SLES 15, mirror entitled repositories, and verify HTTPS registration and package access from a test client.
Connect SLES 15 to AD with YaST’s SSSD-based logon management, then verify directory lookup, domain login, and Kerberos tickets.
Set up the right Live Patching path for SLES 16.0 or 15 SP7, apply eligible kernel fixes, and confirm what is active without confusing it with a reboot-required kernel update.
Load a custom SLES 15 kernel module without disabling Secure Boot. Match the running kernel, sign the .ko file, enroll a MOK key, and verify loading.
SLES 15 SP5 can migrate online to SP6, but each node must reboot. Use a tested rolling upgrade or blue-green cutover to keep workloads reachable.
Use SUSE’s supported STIG profile to scan SLES 15, test remediation, review remaining findings, and retain assessment evidence.
Trace a failed Cockpit connection through DNS, port 9090, the systemd socket, firewalld, TLS, and login settings using current SUSE guidance.
