Files
claudetools/.claude/memory/reference_client_docs_structure.md
Howard Enos 8d975c1b44 import: ingested 160 files from C:\Users\howar\Clients
Howard's personal MSP client documentation folder imported into shared
ClaudeTools repo via /import command. Scope:

Clients (structured MSP docs under clients/<name>/docs/):
- anaise       (NEW)  - 13 files
- cascades-tucson     - 47 files merged (existing had only reports/)
- dataforth           - 18 files merged (alongside incident reports)
- instrumental-music-center - 14 files merged
- khalsa       (NEW)  - 22 files, multi-site (camden, river)
- kittle       (NEW)  - 16 files incl. fix-pdf-preview, gpo-intranet-zone
- lens-auto-brokerage (NEW) - 3 files (name matches SOPS vault)
- _client_template    - 13-file scaffold for new clients

MSP tooling (projects/msp-tools/):
- msp-audit-scripts/ - server_audit.ps1, workstation_audit.ps1, README
- utilities/         - clean_printer_ports, win11_upgrade,
                       screenconnect-toolbox-commands

Credential handling:
- Extracted 1 inline password (Anaise DESKTOP-O8GF4SD / david)
  to SOPS vault: clients/anaise/desktop-o8gf4sd.sops.yaml
- Redacted overview.md with vault reference pattern
- Scanned all 160 files for keys/tokens/connection strings -
  no other credentials found

Skipped:
- Cascades/.claude/settings.local.json (per-machine config)
- Source-root CLAUDE.md (personal, claudetools has its own)
- scripts/server_audit.ps1 and workstation_audit.ps1 at source root
  (identical duplicates of msp-audit-scripts versions)

Memory updates:
- reference_client_docs_structure.md (layout, conventions, active list)
- reference_msp_audit_scripts.md (locations, ScreenConnect 80-char rule)

Session log: session-logs/2026-04-16-howard-client-docs-import.md

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-16 19:43:58 -07:00

1.7 KiB

name, description, type
name description type
Client Documentation Structure 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/. 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.