How to Add a User to a Group in Linux for Camera Access

The short answer

To add an existing user to an existing group on most Linux distributions, run the following command with administrator rights. Replace groupname and username with real values.

sudo usermod -aG groupname username

For webcam access, the group is usually called video. The command for that case looks like this:

sudo usermod -aG video username

The new membership takes effect only after that user logs out and logs back in. Existing sessions keep the old group list.

The -a flag means append, and it matters. If you run usermod -G without -a, the user is removed from every supplementary group not listed in the command. That can take away administrator (sudo or wheel) membership and other access.

Do you need the video group at all?

Not always. On many current desktop distributions, the system automatically gives the person logged in at the computer access to cameras and similar devices for the length of their session. If your camera already works in a local desktop session, adding yourself to the video group changes nothing for you.

Group membership is more likely to matter in these situations:

• You access the camera over SSH or from a remote session.
• A background service or another user account needs to read the camera.
• You use a minimal or server setup without a full desktop session manager.
• The device permission check below shows that your user cannot open the camera device.

Step by step: give a user camera access

1) Find out which group owns the camera device. Linux exposes webcams as device files named /dev/video0, /dev/video1 and so on. List them:

ls -l /dev/video*

The output shows an owner and a group for each device, for example root and video. The group shown here is the one to join. If no /dev/video entries appear, the system has not detected the camera. In that case, adding users to groups will not help, so check the connection or driver first.

2) Check the user's current groups:

groups username

3) Add the user to the group that owns the device, keeping their existing groups:

sudo usermod -aG video username

Another command does the same job on most distributions. It adds one user to one group and never touches their other groups:

sudo gpasswd -a username video

4) Log out completely and log back in. A full reboot also works. To test in a single terminal without logging out, you can start a shell that uses the new group:

newgrp video

newgrp only changes that one terminal. Apps you already have open, such as your browser, still need a fresh login.

Verify the result

Once you have logged back in, confirm that the membership is active in your current session:

id

The group should appear in the groups= list. The groups username command reads the saved configuration, so it can show the group before you log back in. The id command, run with no arguments, shows what your current session actually has.

Seeing the group in that list means the permission is in place. It does not prove the camera works. To check that, open a camera app or a browser camera test and look for a live image. Video quality on a call is a third, separate question. It depends on lighting, resolution settings and network conditions, and group membership does not affect it.

If the camera still doesn't work

• Another app is using it: many webcams can be opened by only one program at a time. Close other video apps.
• The browser blocked it: browsers ask for camera permission separately for each site. Check the camera icon near the address bar and the browser's privacy settings.
• The app is sandboxed: apps installed as Flatpak or Snap packages have their own camera permissions, managed through the package system or the desktop's privacy settings. Group membership alone may not open the camera to them.
• A privacy switch or shutter is engaged: some laptops have a hardware camera switch, a keyboard key or a physical cover.
• The group name differs: if ls -l /dev/video* showed a group other than video, add the user to that group instead.

A note on microphones and the audio group

Some older guides suggest adding users to the audio group to fix microphone problems. On desktops running modern sound servers such as PipeWire or PulseAudio, this is generally discouraged. Audio access is normally handled per login session, and membership in the audio group can interfere with that handling, especially when several users share a machine. If your microphone is detected but shows no input, check the input device and level in your sound settings first.

Related tasks

• Create a new group: sudo groupadd groupname
• Remove a user from a group: sudo gpasswd -d username groupname
• List all members of a group: getent group groupname

These commands are standard on mainstream distributions, but menus, default groups and device permissions vary between distributions and versions. If your system behaves differently, go by your distribution's own documentation.