Advisor Access
Advisor route access is blocked.
Sign in through the dev-auth harness, then bootstrap app-owned founder/internal records before opening advisor surfaces.
- Route
- /advisor-onboarding
- Access state
- Signed out
- Proxy boundary
- seen
- Diagnostic state
- No Clerk session
- Clerk session
- not present
- App-owned identity
- not resolved
- Advisor access
- not checked
- Route path
- /advisor-onboarding
- Proxy boundary
- seen
- Has cookie header
- no
- Has Clerk-like cookie
- no
- Clerk-like cookie count/classification
- 0 / none
- Has authorization header
- no
- Has forwarded host
- yes
- Has host
- yes
- Server helper used
- app_router_auth_current_user
- Server auth sees session
- no
- Server auth reason
- no_server_session_or_user
Clerk session presence does not grant Advisor AiDE access by itself. Advisor routes require explicit app-owned founder/internal workspace, advisor seat, role assignment, and entitlement records.