g.access(1)

📦
version 8.4.2 · 8 versions
, in fedora 44

✨ g.access(1) — the GRASS GIS girlie manual ✨

okay so bestie, welcome to g.access from the GRASS GIS User's Manual 💖 this one is short and sweet and honestly kind of iconic.

🌸 NAME 🌸

g.access — controls access to the current mapset for other users on the system.

If no option given, prints current status. (yes really, no options = it just tells you what's up 👀)

🎀 KEYWORDS 🎀

general, map management, permission

🦋 SYNOPSIS 🦋

g.access
g.access --help
g.access [group=string] [other=string] [--help] [--verbose] [--quiet] [--ui]

🌟 Flags

  • --help — print the usage summary, like a little cheat sheet 🫶
  • --verbose — verbose module output, she's chatty
  • --quiet — quiet module output, she's mysterious 🤫
  • --ui — force launching the GUI dialog

🌈 Parameters

  • group=string — access for group. Options: grant, revoke
  • other=string — access for others. Options: grant, revoke

💅 DESCRIPTION 💅

This program lets you control access to the current mapset. Normally, any user can read data from any GRASS mapset. But sometimes it's desirable to prohibit access to certain sensitive data. The g.access command allows a user to restrict read and execute access to the current mapset (see UNIX chmod command). g.access will not modify write access to the current mapset. Not me messing with read perms but leaving write alone, lowkey respectful.

The user may, for example, allow only users in the same UNIX group to read data files in the mapset, or restrict the mapset to personal use only. Main character energy: private mapset, no visitors 🚪✨

🔥 NOTES 🔥

Under GRASS, access to the mapset PERMANENT must be open to all users. This is because GRASS looks for the user's default geographic region definition settings and the project TITLE in files that are stored under the PERMANENT mapset directory. The g.access command, therefore, will not allow you to restrict access to the PERMANENT mapset.

fr fr, PERMANENT is communal property and you cannot gatekeep it. The way that GRASS NEEDS those region settings and the project TITLE out of PERMANENT... it's giving shared resources, bestie. g.access said nope 💀

The g.mapsets command isn't smart enough to tell if access to a specified mapset is restricted, and the user is therefore allowed to include the names of restricted mapsets in his search path. However, the data in a restricted mapset is still protected; any attempts to look for or use data in a restricted mapset will fail. The user will simply not see any data listed for a restricted mapset.

So like, you can put the restricted mapset name in your search path and nothing stops you from typing it, but you're just gonna see... nothing. Empty. Ghosted 🙈 the protection is real even if the detection isn't. iykyk.

UNIX filesystem access controls and g.access actions are not supported by MS-Windows. Windows girlies, this one is not for you, sorry 😭

👑 SEE ALSO 👑

🍓 AUTHOR 🍓

Michael Shapiro, U.S. Army Construction Engineering Research Laboratory

⭐ SOURCE CODE ⭐

Available at: g.access source code (history)

Accessed: Saturday Jan 17 05:40:39 2026

Main index | General index | Topics index | Keywords index | Graphical index | Full index

© 2003-2025 GRASS Development Team, GRASS GIS 8.4.2 Reference Manual

and that's the whole vibe check for g.access(1), running on GRASS 8.4.2 🌈 thank you for coming to my TED talk, go grant and revoke responsibly, slay 💖✨🎀🦋

📦 where this page comes from