Grixel gives each person access to the parts of the depot they need, and nothing else. This page explains what that looks like from your side as a user.
#You see what you've been granted
Your administrator grants you access to particular paths — a project, a team's area, a shared set of standards. Everywhere you look — listings, search, history, your AI assistant's view — you see only those paths.
#"Not found" can mean "not yours to see"
This is the one behavior worth understanding. If you try to reach a path you don't have access to, Grixel says not found — exactly what it would say if the path didn't exist at all.
grixel ls /companies/acme/games/unreleased-thing
# not found: /companies/acme/games/unreleased-thingThat's deliberate. Grixel doesn't say "access denied", because saying so would tell you the path exists. So:
- If you get "not found" for something a colleague can see, you probably haven't been granted access — ask your administrator, don't assume it's a bug.
- There's no way to tell, from the outside, whether a "not found" path is hidden or genuinely absent. That's the point.
#Check who you are
If something isn't visible and you expected it to be, confirm which account you're signed in as:
grixel whoami#Private space that's just yours
You can carve out a private folder that only you (and administrators) can see, without asking anyone to set it up:
grixel private create scratchUse it for work in progress you don't want visible to the team yet.
#Secrets that stay secret
For genuinely sensitive values — a .env, API keys — use
encrypted secrets instead of a private folder. These are encrypted on
your machine before they're stored, so even someone who can read the raw
storage can't read them:
grixel key init # one-time: create your key
grixel secret add .env # start protecting a file
grixel secret push # upload the encrypted version
grixel secret pull # bring it back on another machineSee the command reference for the full set.