Instant access removal for former staff

Offboarding failures in chat are quiet. Nobody notices that a former supervisor is still in the “North Site – Ops” group on their personal phone until a client’s alarm code shows up in a screenshot. The fix is not complicated, but it has to be fast and it has to happen every time. This page explains how removal works in C Chat and where its limits are.

Short answer: remove from the team, keep the history

Revoking chat access for a former employee in C Chat is one action: an owner or admin removes the person from the team. The effect is immediate:

• The person stops seeing every group in that team.
• The groups and their history stay with the team.
• Owners and admins can still audit and export those groups later.

This is the key difference with personal messaging groups, where the group often belongs to whoever created it and a departing employee may even be its administrator. In C Chat, the team owns its groups. The owner and admin roles explain who can add and remove people.

How instant removal works in C Chat

For any team

Use the full offboarding checklist for chat access so this step sits next to returning keys and badges. The same-day offboarding use case shows how operations teams build it into their routine.

For security companies on CGuard Pro

Access is tied to the operation. Site groups contain the guards on duty, the office and the client. With on-duty access, guards who are off duty cannot read site groups, and when a guard is fired in CGuard Pro they are removed instantly. There is no gap between the termination and the end of access. For the specific workflow, see removing former guards from site chats.

Who can see what after removal

Item	Removed person	Team owners and admins
Team groups	No access	Full access, can audit and export
Messages they posted in groups	No access	Remain in group history
Their direct messages with others	Still private between participants	Not visible
Files they downloaded earlier	Still on their device	Cannot recall them

What it means for owners, admins and members

Owners and admins should treat chat access like any other system account: granted when needed, removed on the last day. Structure helps. When groups follow sites and departments, as in structuring groups for a growing team, it is obvious which groups a role touched.

Keep at least two admins per team. If your only admin leaves, removal and audits depend on a person who is no longer there.

Members benefit too. Removal protects the information colleagues shared with that person in good faith, such as schedules, client contacts and photos from sites.

This approach follows least privilege: people should keep access only while their role needs it.

Honest limits and caveats

• No remote wipe. C Chat does not offer device management. Content the person saved, screenshotted or forwarded before leaving stays with them.
• Direct messages remain possible. Any C Chat user can message any other. If a former employee contacts staff in an unwelcome way, block and report.
• Removal is a human step for regular teams. Outside the CGuard Pro integration, nobody is removed automatically. Put it in your HR exit process.
• Exports still exist. If you exported a group before the person left, that file follows your own storage rules.

Getting started

If your team still runs on personal groups, moving to C Chat gives you a clean starting point: one team, groups owned by the business, and a single place to remove access. Open getcchat.com/c to create the team, then read what admins can audit and export to plan your records.