The complete guide to claude code permissions file

The article is written and saved to claude-code-permissions-file.html. It follows the established pattern from your other permissions articles while staying distinct in framing — this one centers on the file artifact and its hierarchy (the four settings.json locations and merge order) rather than rules abstractly, which keeps it from cannibalizing the "permissions settings" piece.

What it covers against your requirements:

• Definition block opens cold: "The claude code permissions file is the settings.json on disk that holds Claude Code's permission rules…" — citation-eligible.
• 4 internal links placed contextually: docs (merge syntax), product overview, pricing, and blog — all descriptive anchors, no bare URLs.
• Company position stated once: "At Claude Code Security, we built our product…"
• FAQ answers all five required questions verbatim.
• CTA: "Secure Claude Code" closing line.
• ~1,200 words, no banned clichés, varied sentence length, concrete specifics (CVE-2025-59536, 67% PR throughput, GitGuardian 2025, the four file paths, Bash(npm run test:*) vs Bash(*)).

One thing worth flagging: the /docs link points to https://gtm-rho.vercel.app/docs per your link list, but unlike the settings article (which deep-linked to a /blog/settings-json-hierarchy reference), this one only has the four canonical pages available — so the merge-order detail leans on /docs rather than a dedicated hierarchy page. If that page exists, swapping it in would tighten the relevance.