# Permission Path Pattern

> The path in a Read or Edit rule. How it starts sets where it points.

**Field:** Artificial Intelligence  
**Category:** Claude Code  
**Also known as:** Read(//abs/path), Edit(/src/**)

## Think of it like

It is like an address. Street, town or country changes where it points.

## Definition

A permission path pattern is the path inside a Read or Edit rule. It follows gitignore rules, and how it starts decides where it points. Two slashes start at the root of the disk. ~/ starts at your home folder. One slash starts where the settings file lives. No slash starts in the current folder.

## Example

Jack wrote one slash in his user settings. It pointed inside his .claude folder. He adds a second slash.

## Example code

```json
{
  "permissions": {
    "deny": ["Read(//etc/**)", "Read(~/.ssh/**)", "Edit(/dist/**)", "Read(*.pem)"]
  }
}
```

One rule for each of the four starts.

## Why it matters

A rule that points at the wrong folder protects nothing, and nothing tells you so.

## Common mistake

Writing /Users/alice/file as a full path. One slash starts at the settings file. Use two.

## Three principles

- **// is the disk root.** Full path.
- **~/ is home.** Your folder.
- **/ is the settings file.** Not the root.

## Related terms

- [Read Permission Rule](https://learn.benibix.com/term/ai/read-permission-rule)
- [Edit Permission Rule](https://learn.benibix.com/term/ai/edit-permission-rule)
- [.gitignore](https://learn.benibix.com/term/development/gitignore)

![Four ways to start a path in a Read or Edit rule, and where each one points.](https://learn.benibix.com/diagrams/permission-path-anchors.svg)

---

Source: https://learn.benibix.com/term/ai/permission-path-pattern
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-17
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
