SecurityP1

Access should be narrow, visible, and revocable.

42flows connects to publishing systems and analytics, so security has to be boring and explicit. We separate public crawlable pages from private dashboards and use scoped credentials where possible.

Publishing access

WordPress uses application-password style access. GitHub/Nuxt publishing uses repository-scoped workflows. Private dashboard routes stay blocked from public crawlers.

Diagnostics access

Diagnostic tokens are short-lived, read-only, and built so a founder can let a coding agent inspect production state without sharing an admin session.