[Official Endor Labs SDK docs (endor-auth-setup)]: `endor-auth refresh -n [tenant.child]` logs in against the root segment (tenant) only, so do not assume a child namespace passed to refresh becomes your API list path. Set ENDOR_NAMESPACE or pass -n on the workflow CLI you run after auth. Precedence for SSO: the refresh flag, then ENDOR_NAMESPACE in shell, then .env, then endorctl config.yaml. Token lifetime gotchas: one Client instance holds its bearer token in memory, expiry prints a one-time stderr warning within 30 minutes, and an expired token fails closed with UnauthorizedError. Refresh does not touch .env or os.environ, and child shells never inherit the in-memory token, so rerun `endor-auth refresh` in each new process.

Context: Official docs (endor-auth-setup SKILL.md): documents two SSO gotchas that trip agents. `endor-auth refresh` uses only the root segment of the tenant for the IdP login, while report workflows use the full namespace path for list scope. Also, a refreshed bearer token lives in memory only: child shells do not inherit it and the SDK client never writes it to disk.