---
name: Client Documentation Structure
description: Howard's MSP client docs live under clients/<name>/docs/ with a standard subfolder layout (overview, network, servers, cloud, security, rmm, issues). Template at clients/_client_template/.
type: reference
---

Each active client has structured Markdown documentation under `clients/<client-name>/docs/`:

| File / Folder | Purpose |
|---|---|
| `overview.md` | Company info, contacts, environment summary, device counts |
| `network/topology.md` | Switches, APs, cabling, interconnects |
| `network/vlans.md` | VLAN table, subnets, inter-VLAN routing |
| `network/dns.md` | DNS servers, zones, records, forwarders |
| `network/dhcp.md` | Scopes, reservations, relay config |
| `network/firewall.md` | Rules, NAT, VPN, interfaces |
| `network/wifi.md` | SSIDs, security, AP assignments |
| `servers/<name>.md` | Per-server docs (use `server_template.md`) |
| `cloud/m365.md` | Tenant, licensing, Exchange, Entra ID |
| `cloud/azure.md` | Subscriptions, VMs, networking |
| `security/antivirus.md` | EDR/AV product, deployment status |
| `security/backup.md` | Backup jobs, targets, DR plan |
| `rmm/rmm.md` | RMM product, agent counts, patch policy |
| `issues/log.md` | Historical incident log with root causes |
| `billing-log.md` | Per-client billing / work log |

Clients currently documented (imported 2026-04-16 from Howard's `C:\Users\howar\Clients`):
anaise, cascades-tucson, dataforth, instrumental-music-center, khalsa, kittle, lens-auto-brokerage.

Credentials NEVER go inline in these docs — reference SOPS vault instead:
`clients/<name>/<system>.sops.yaml` field path.

The template at `clients/_client_template/` is the scaffold for new clients.
