Sign in and environments

Sign in and environments

Use the environment that matches the work you are doing. Do not capture documentation screenshots or run mutating workflow tests against production.

Environment	Use	Documentation screenshot policy
Local	Engineering validation and static documentation checks.	Allowed for layout checks only.
UAT	Operator acceptance and synthetic workflow screenshots.	Preferred capture target.
Staging	Release verification when UAT cannot represent the workflow.	Allowed with synthetic data.
Production	Live editorial operations.	Do not use for screenshot capture or synthetic mutation.

Sign in

1. Open /cms.
2. If Cloudflare Access appears, complete the existing operator Access challenge.
3. Use the PowerAdvice Clerk sign-in flow.
4. Wait for the left rail labeled PowerAdvice CMS sections.
5. Confirm the environment label in the CMS top bar before editing records.

Authenticated tests and screenshots

PowerAdvice already maintains Clerk-backed Playwright auth helpers:

• tests/e2e/cms-auth.setup.ts
• tests/e2e/cms-auth-helpers.ts
• storage state: tests/e2e/.auth/cms-admin.json

Docs OS uses the same storage-state path in docs-os.config.json. Commands must never print credentials, cookies, Access service tokens, or storage-state contents.