How to delete a group in Linux

Deleting a local group retires an access label that may still be tied to shared directories, service accounts, or old project paths. Removing groups that no longer belong in the permission model keeps ownership reviews clearer and reduces the chance of reusing a stale name for the wrong access role.

Linux resolves group records through the configured account sources, with local groups typically stored in /etc/group and /etc/gshadow. The groupdel command removes the local group entry, but a user can still have that group as its primary GID and existing files can still carry the old group ownership until those dependencies are moved elsewhere.

Delete the group only after every account and path that still depends on it has been updated. groupdel refuses to remove a group that is still the primary group for an existing user, and usermod -g only fixes ownership inside that user's home directory automatically. Files outside the home directory, and groups provided by LDAP, SSSD, Active Directory, or another directory service, must be handled separately.

1. Confirm that the target group currently resolves so the exact group name and numeric GID are known before anything is changed.

   $ getent group projectops
   projectops:x:4200:

   The numeric field after the group name is the GID that can still appear in /etc/passwd and filesystem metadata after the group name is removed.

2. Try the removal first when the goal is to find out whether an account still uses that group as its primary group.

   $ sudo groupdel projectops
   groupdel: cannot remove the primary group of user 'deploysvc'

   groupdel stops here until every affected account is moved to another primary group.

3. Move each affected account to an existing replacement primary group, then confirm the new GID.

   $ sudo usermod -g sharedops deploysvc
   $ id deploysvc
   uid=1001(deploysvc) gid=4201(sharedops) groups=4201(sharedops)

   The replacement group such as sharedops must already exist before it can become the account's new primary group. usermod -g updates old-group ownership inside the user's home directory automatically, but paths outside the home directory still need manual cleanup.

4. Find files and directories that still use the old group ownership in the relevant data path.

   $ find /srv/group-delete-demo -group projectops -printf '%u:%g %p\n'
   root:projectops /srv/group-delete-demo
   root:projectops /srv/group-delete-demo/releases.txt

   Search the application, project, or mount paths that actually use the group instead of scanning the entire filesystem by default.

5. Change any remaining file or directory group ownership before removing the group entry.

   $ sudo chgrp -R sharedops /srv/group-delete-demo
   $ find /srv/group-delete-demo -printf '%u:%g %p\n'
   root:sharedops /srv/group-delete-demo
   root:sharedops /srv/group-delete-demo/releases.txt

   Removing the group first leaves those paths tagged only with the numeric GID, which makes later ownership review and access cleanup harder.

   Related: How to change ownership of files and directories in Linux

6. Delete the group after user and file dependencies have been moved away.

   $ sudo groupdel projectops

   Some distributions also provide wrappers such as delgroup, but groupdel is the common cross-distribution command for local group removal.

7. Confirm that the group no longer resolves from the local account database.

   $ getent group projectops || printf 'projectops not found\n'
   projectops not found

   If cleanup is complete, the old group name no longer resolves and the earlier data-path check no longer shows any paths owned by that group.