FS_CHGRP(1)

✨ NAME ✨

okay bestie, say hi to fs_chgrp — it changes the group for an object stored within AFS, and this whole page is from the AFS Command Reference. Also important: it’s [Windows only]. Like, Windows-only Windows-only. 💅

---

🎀 SYNOPSIS 🎀

fs chown -group <user/group> -path <dir/file path>+
    [-literal][-help]

yes, the synopsis says fs chown exactly like that — copy-pasta is sacred, bestie, do not “fix” it. 🫶

---

💅 DESCRIPTION 💅

The fs chgrp command assigns the specified group to each object specified with the -path option. Slay, group assignment era. ✨

If you pass -literal, the targets of symlinks and mountpoints are not resolved. That means the group of the symlink or mountpoint itself can be assigned. Iconic behavior, honestly. 🦋

The group can be specified by name or by number. If you use a name, that name gets resolved to its numeric value by querying the protection server in the cell for each specified -path object. Fr fr, each object. 💖

Wanna see the current group? Use the fs examine command. Go look, bestie. 👑

---

🚨 CAUTIONS 🚨

Explicit or implicit administrator access rights are required to be able to change the group of an object stored in AFS. No cap, you need the juice for this. 🔥

This command is available in versions of OpenAFS for Windows 1.5.61 and higher. So if you’re on something older, it’s giving “not invited to the group chat.” 😭

---

🌈 OPTIONS 🌈

• -group <user/group> — a valid name or number of a user or group identifier in the Protection Service database. That’s the group you’re assigning, bestie. 💜
• -path <dir/file path>+ — names each AFS directory or file on which the group will be set. Partial pathnames are interpreted relative to the current working directory. 🎀

Specify the read/write path to each directory to avoid the failure that results from attempting to change a read-only volume. By convention, the read/write path is indicated by placing a period before the cell name at the pathname’s second level (for example, /afs/.example.com). For further discussion of the concept of read/write and read-only paths through the filespace, see the fs mkmount reference page. 🌸

• -literal — when specified, the targets of symlinks and mountpoints are not resolved. This permits the ownership of the symlink or mountpoint to be assigned. yes, it says “ownership” right there — we keep the original wording, periodt. 🫶
• -help — prints the online help for this command. All other valid options are ignored. Bye to the other flags, they’re not the main character once -help shows up. 💅

---

👑 PRIVILEGE REQUIRED 👑

The issuer must have the "a" (administer) permission on the directory’s ACL, a member of the system:administrators group, be the UID owner of the object, or, as a special case, must be the UID owner of the top-level directory of the volume containing the object. That’s the whole vibe check for permissions. 🔥

---

🦋 SEE ALSO 🦋

fs_examine(1), fs_chown(1)

---

💖 COPYRIGHT 💖

This document was written by Jeffrey Altman and is released under the BSD license. Respect the author, bestie. 🎀

---

— with love, OpenAFS, 2026-06-25 💖