You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When set to `true`, non-superusers can still view and use custom components in flows, but they cannot create new custom components or edit custom component code.
33
33
34
+
## Interaction with catalog governance
35
+
36
+
Catalog governance takes precedence over the custom-code settings on the custom-component create, update, and code-validation endpoints. A catalog block has no superuser bypass.
| Unknown custom source | Not blocked | Enabled | Superuser or admin-only disabled | Allowed |
46
+
47
+
For `POST /api/v1/validate/code`, this policy runs before the source is parsed or imports are inspected. In a restricted custom-code mode, known templates are validated from the trusted server copy, while unknown source follows the same disabled or admin-only rule as the component editor. On custom-component create and update, known blocked template source is rejected before the component is built, and the resolved component type is checked again before request-supplied frontend updates are applied.
48
+
49
+
An active catalog policy fails closed with a temporary `503` response while server template identities are still initializing. An empty catalog policy preserves the default behavior and does not require template identity lookups.
50
+
34
51
## Configure a custom component allow-list
35
52
36
53
`LANGFLOW_ALLOW_CUSTOM_COMPONENTS` works together with optional paths that define which component templates the server loads, and which code hashes are trusted.
@@ -62,4 +79,4 @@ Default is `true`, which preserves existing behavior. The setting has no effect
0 commit comments