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

# Flowker environment-label contract

> Flowker accepts deployment labels beyond the former fixed list, and both prod and production activate production guards.

<Badge stroke icon="calendar-days" iconType="regular">August 17, 2026</Badge> <Badge stroke icon="file-code" iconType="regular">Documentation correction</Badge> <Badge color="red" size="lg" stroke icon="triangle-exclamation" iconType="regular">Action required</Badge>

## Affects

***

Teams that deploy Flowker, especially with production guards or the Tenant Manager secrets backend.

## What changed

***

Both `production` and `prod` enable Flowker's production guards for request, XSD-schema, and OpenAPI-schema authentication. Flowker accepts other environment labels. `ENV_NAME` is required to be non-empty only when `FLOWKER_SECRETS_BACKEND=tenant-manager`, because it forms part of the secret path.

This is a documentation correction that aligns the environment reference with implemented behavior. Runtime behavior did not change.

## Impact

***

**Classification: Action required.** A deployment using `ENV_NAME=prod` must satisfy production guard requirements. Tenant Manager deployments must provide a non-empty environment label.

## What you need to do

***

Review deployment values. Verify authentication settings for both `production` and `prod`, and set a non-empty `ENV_NAME` whenever the Tenant Manager secrets backend is configured.

## Resources

***

* [Flowker environment variables](/en/products/flowker/flowker-environment-variables)