Remove guard access from every site chat, the moment they leave

Every security company has the same uncomfortable scenario: a guard is let go on bad terms and, a week later, is still in the WhatsApp group for a client site where alarm codes and patrol times are shared. Nobody did it on purpose; the group was created by a supervisor’s phone, and removing people was nobody’s job. Offboarding in chat is a security control, not admin housekeeping.

Why guard offboarding breaks down without a system

• Groups belong to individuals. On personal apps, whoever created the group controls it. If that supervisor is on leave, nobody can remove the guard.
• Guards sit in many groups. A guard who covered five sites has five groups to clean, and one is always forgotten.
• HR and operations are disconnected. The termination is processed in one system; the chats live somewhere else.
• Rotations blur access. Guards who covered a site once stay in that site’s group indefinitely.

The general principle for all staff is in instant access removal for former staff; this page applies it to guards.

The workflow in C Chat

With the CGuard Pro integration, offboarding follows the employment record:

Before offboarding even happens, on-duty access limits exposure: guards can only read a site group while on duty. A guard on days off, on leave or between assignments sees nothing.

Without CGuard Pro, the same result is achieved by an admin removing the guard from the C Chat team, which ends access to all of its groups at once.

Group setup and message template

Keep the structure simple so removal is predictable: one team for the security company, one group per site, and admin rights held by operations, not by individual supervisors’ personal accounts. Pin this offboarding checklist in the supervisors’ group:

OFFBOARDING – [guard name] – [date] ☐ Employment ended in CGuard Pro (or removed from C Chat team) ☐ Sites affected: … ☐ Clients informed where needed ☐ Codes / keys / fobs changed ☐ Equipment returned: radio, uniform, badge

Roles, oversight and records

The company owns the team; operations managers are admins. Because access is tied to the team and, with CGuard Pro, to the schedule, removal doesn’t depend on who created a group.

C Chat encrypts messages with TLS in transit and AES-256 at rest using per-organization keys. Under the auditable model, security companies using CGuard Pro can audit groups and security-related chats with guards and office, which matters if a dispute follows a termination. That oversight is covered in security company oversight of CGuard Pro groups. Direct messages between people remain private.

A clean offboarding protects every other workflow: incident reports keep their evidence, shift handovers reach only current guards, and client updates go to people the client can trust. Residential clients such as condos and HOAs are particularly sensitive to this.

Common mistakes to avoid

• Groups created from a supervisor’s personal account. Admin rights should sit with the company.
• Assuming chat removal is enough. Change codes and collect keys too.
• Removing too late. Offboard in chat the same moment employment ends, not at the end of the week.
• Deleting the history. Keep it; you may need it for a claim or a client review.

Guards who work alone and are offboarded mid-rotation also need their check-in routine handed to someone else; see lone guard check-ins.

Getting started

If your company runs CGuard Pro, enable the C Chat integration so site groups follow the schedule and terminations. Otherwise, set up a company-owned team with one group per site and make operations the admin. Read the security companies page and start at getcchat.com/c.