Folder and File Level Access Restriction Needed

**Current Behavior:**
Currently, if a user has access to the **Team** directory, they can view **all** its subfolders and files, regardless of individual folder or file permissions.

```
Team/
├─ Folder/ (RW)
│ ├─ File.txt (RW)
│ │ └─ Sub-Folder/ (Restricted: X)
│ └─ Folder-Restricted/ (Restricted: X)
└─ Folder-2/ (R)
└─ File-2.txt (R)
```

At present, users with access to `Team` can still navigate into `Folder-Restricted/` and `Sub-Folder/`, even though those are intended to be restricted.

---

**Expected Behavior:**

* Access should be **controlled at folder and file level**, not just inherited from the parent (`Team`).
* If a folder or file is marked as **Restricted (X)**, it should **not be visible or accessible** to users without explicit permission.
* Permissions should respect:

* **R** (Read): View only
* **RW** (Read/Write): View and modify
* **X** (Restricted): No access

No files, tests, or entry points are named. Start by tracing how access inherited from the Team directory is currently handled, then verify that restricted folders and files are hidden and inaccessible while R and RW permissions retain their stated behavior.

Written by the indexing model from the issue text.