> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aitasker.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Public Team State Overrides

> Public endpoint: sparse list of team visibility overrides keyed by slug.

Same pattern as `/public/task-type-overrides`. The frontend ships the
full team catalog statically (`frontend/src/lib/team-catalog.ts`), so
this endpoint only needs to return the exceptions from the default
`live` state. No auth.

We also honor the `teams_enabled` env kill-switch — if teams are
disabled platform-wide, every team effectively becomes `hidden`,
regardless of its DB state. This keeps the env-flag-wins-on-conflict
semantics from `app.services.visibility.effective_state` consistent
across every public surface that reads team state.

Frontend treats missing slugs as `live`.



## OpenAPI

````yaml /openapi.json get /api/v1/public/team-state-overrides
openapi: 3.1.0
info:
  title: AITasker
  version: 0.1.0
servers: []
security: []
paths:
  /api/v1/public/team-state-overrides:
    get:
      tags:
        - Public
      summary: Public Team State Overrides
      description: |-
        Public endpoint: sparse list of team visibility overrides keyed by slug.

        Same pattern as `/public/task-type-overrides`. The frontend ships the
        full team catalog statically (`frontend/src/lib/team-catalog.ts`), so
        this endpoint only needs to return the exceptions from the default
        `live` state. No auth.

        We also honor the `teams_enabled` env kill-switch — if teams are
        disabled platform-wide, every team effectively becomes `hidden`,
        regardless of its DB state. This keeps the env-flag-wins-on-conflict
        semantics from `app.services.visibility.effective_state` consistent
        across every public surface that reads team state.

        Frontend treats missing slugs as `live`.
      operationId: public_team_state_overrides_api_v1_public_team_state_overrides_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}

````