Turn on features with flags
Some features are off by default on a Self-Managed instance, and some need a config value only you can set. You turn features on with feature flags in Flagsmith.
Turn a flag on in Flagsmith
Section titled “Turn a flag on in Flagsmith”Change flags in Flagsmith. Flag names there are lowercase. To turn a flag on for the whole instance, turn it on in the environment. To turn it on for some organizations only:
- Under Segments, create a segment, such as “pilot organizations”, with a rule on the trait
orgId, operator In, and the organization IDs separated by commas. - Open the flag, go to Segment Overrides, add the segment, and turn it on there. Set a value if the flag has one.
- Leave the flag off in the environment.
A percentage rollout below 100% splits by user, not by organization. Pages shown before sign-in see only the environment’s setting.
Let API Action steps call internal hosts
Section titled “Let API Action steps call internal hosts”API Action steps can’t call hostnames that resolve to private network addresses. To allow it, turn it on for both the api and task-worker-ts applications:
kindo config set overrides.serviceEnv.api.API_ACTION_ALLOW_PRIVATE_ENDPOINTS=truekindo config set overrides.serviceEnv.task-worker-ts.API_ACTION_ALLOW_PRIVATE_ENDPOINTS=trueApply the change:
kindo config applyIt shows what it will change and asks first.
Internal targets need a fully qualified hostname that resolves to the private address. When the step is saved, Kindo rejects IP addresses and single-label hostnames. Link-local addresses, including 169.254.0.0/16, and cloud metadata services stay blocked.
