Planning guide
Role-based pages
Publish one site while giving each role the right pages.
Switch between visitor and member views to experience allowed content, protected routes, and a helpful access state.
Member library
Practical guidance, beautifully organized.
Clear answers, focused stories, and thoughtful tools help every reader find the next useful step.
Planning guide
A calmer way to plan a renovation
Working with pros
Questions to ask before signing
Design basics
How to compare material samples
Downloads
The room-by-room budget worksheet
Local planning
When a project needs a permit
Getting started
Build a useful project brief
One connected experience
Designed around people
Practical guidance, beautifully organized.
Clear answers, focused stories, and thoughtful tools help every reader find the next useful step.
- Useful detail appears where a visitor expects it.
- Every action provides an immediate, understandable response.
- The experience stays focused from mobile through desktop.
Fieldnote Journal
Role-based pages
Switch between visitor and member views to experience allowed content, protected routes, and a helpful access state.
Member library
Practical guidance, beautifully organized.
Clear answers, focused stories, and thoughtful tools help every reader find the next useful step.
Featured story
A calmer way to plan a renovation
Clear answers, focused stories, and thoughtful tools help every reader find the next useful step.
Professional workflow
Page Role Access, from first action to operational proof.
Run Page Role Access with a guided setup checklist, live readiness checks, drift-aware snapshots, a privacy-safe operations trail, and support-ready diagnostics.Guided scenario lab
Test Page Access
- 1Select the exact WordPress roles allowed to open each protected pageDealer is in the page role set; nonmatching users and guests receive the plugin’s fixed 403 response.
- 2Leave pages public when no allowed roles are selectedSource-reviewed capability included in the current installable package.
- 3Return a fixed 403 response when a guest or nonmatching role opens a protected pageSource-reviewed capability included in the current installable package.