Max Peintner

We decided to provide an attribute from the backend where allowed formats are defined. Just like supportedLanguages

discussed it with @livio-a. required task is the following https://github.com/zitadel/zitadel/issues/4256

When considering the Option B, the current privatelabeling policy could be extended with: ``` theme: "system" | "cookie" | "light" | "dark"; secondaryColor: string; darkSecondaryColor: string; logo: { position: "LEFT"...

when selecting a font, a user could be prompted to insert a google fonts css url like https://fonts.googleapis.com/css2?family=Ibarra+Real+Nova:ital,wght@0,400;0,500;0,600;0,700;1,400;1,500;1,600;1,700&family=Montserrat+Alternates:ital,wght@0,400;0,500;1,400&family=Ubuntu&display=swap then all required fonts and css could be fetched from that origin...

The above extension of the policy does not include coloring of the UI elements as they are dependent on the generated palettes. @juergrinaldi I like your mock of the new...

This will be the fix https://github.com/zitadel/zitadel/pull/2666 but it's behaviour has still to be tested for V2

I can confirm this is an eventual consistency issue. What's missing though is toast messages after adding, clearing the flow. Added them here #4247

The PR fixed some toast messages but not eventual consistency. It's still a TODO until behavior is consistent. I'll add a task for this and other places where eventual consistency...

This fixes the design and ensures usability.. limiting the length should imo fixed backend and frontend side in another PR

looking good, but I would add an additional test where a human user is then logged in and checked for the new roles (user grants) in the granted projects of...