FE: Allow AI Catalog flows to be at Beta maturity level, while other AI Catalog features are GA
About
There is a backend counterpart issue for this: #577764 (closed).
Currently, the entire AI Catalog is at the same maturity level (Experiment, and soon GA).
However, flows should not be part of the AI catalog's GA, and should independently move from Experiment -> Beta -> GA.
Problem
Customers must opt in to Experimental and Beta AI Features to use them. This allows customers control over the maturity-level of the AI features they use.
Otherwise, they should not be able to use those features.
As currently, the entire AI Catalog is at the same maturity level, we need to give flows its own maturity level independent from the AI Catalog to ensure we fulfil the compliance expectations of customers not being able to use flows unless they have opted-in to experimenta/beta AI features.
Proposal
The frontend will need to handle the flow feature being at a different level of maturity.
- Flows should be hidden when the feature is Experiment/Beta and the project has not opted-in to Experimental/Beta AI Features
- The UI should label the maturity of flows as Experiment/Beta
(Note, the backend will be updating its permissions to account for different AI features to be at different maturity levels #577764 (closed)).
Show/hide features
At the project-level and group-level, we should hide flows when they are Experimental/Beta if the project has not opted-in to Experiment/Beta AI features.
The backend #577764 (closed) should make available to the frontend a boolean property to determine if the flows features should be presented in the UI. This will be similar to how feature flag checks work.
Please discuss with the backend counterpart how best to supply the booleans - the implementation of the backend for this is currently open and waiting input from the frontend counterpart!
Maturity labels
(Note, in these examples Experiment is used as the label, but it would be Beta instead).
We should signal the maturity level when viewing a flow:
When creating/editing a flow:
And when selecting different kinds of flows (if the different flows are at different maturity levels):


