---
title: Lobby
---

AuthProxy uses the lobby to finish onboarding when a user cannot enter the application directly
after authentication.

Use the lobby documentation based on the onboarding outcome you need:

- [Invitation for Creating Organization](/authproxy/configuration/lobby/invitation-for-creating-organization/) — invite a user
  who should create a new organization after they sign in.
- [Invitation to Organization](/authproxy/configuration/lobby/invitation-to-organization/) — invite a user directly into an
  existing organization.
- [Registration](/authproxy/configuration/lobby/registration/) — let a user start a self-serve registration flow that ends in
  organization creation. If the user should join an existing organization, invite them instead.

## Shared configuration

All lobby-related settings live under `Cratis:AuthProxy:Invite:Lobby`:

```json
{
  "Cratis": {
    "AuthProxy": {
      "Invite": {
        "Lobby": {
          "Frontend": { "BaseUrl": "http://lobby-service:3000/" },
          "Backend": { "BaseUrl": "http://lobby-service:8080/" },
          "Registration": { "BaseUrl": "http://lobby-service:3000/register" }
        }
      }
    }
  }
}
```

The `Lobby` object uses the standard [`Service`](/authproxy/configuration/services/) shape.

| Property | Type | Description |
|----------|------|-------------|
| `Frontend.BaseUrl` | `string` | URL used for lobby redirects after onboarding or when tenant resolution fails. |
| `Backend.BaseUrl` | `string` | Optional backend API URL for the lobby service. |
| `Registration.BaseUrl` | `string` | Optional URL used after `GET /register` completes successfully. |

## Lobby fallback

Tenant resolution runs before invite and registration handling.

When AuthProxy cannot resolve a tenant and a lobby frontend is configured, it redirects the user to
`Lobby.Frontend.BaseUrl` unless the request is already an onboarding bootstrap path such as
`/invite/<token>` or `/register`.