A list is the group of people a team plans to work with, for one purpose somebody wrote down. The list is not the thing that makes an engagement defensible. The documented need recorded against it before anyone is selected for paid work is, and every revision of that need is kept. Open a list to read them.
No identity provider is selected, so there is no user to make this request as. That is a statement about how this deployment is configured and not about your account: nothing here says you are signed out, because nothing here knows who you are.
Behind this: the expert lists this account holds, the documented need recorded against each one, and which of them has nobody selected for paid work yet. No request was sent, so nothing on this screen is a guess about whether the service is up.
To see it on a development stack, run scripts/dev_up.sh and start the web application with AUTH_PROVIDER=e2e and SKEPSIS_DEMO_TOKEN_A set to the token that script mints. The harness refuses to load in a production build, or against an API that is not on this machine.