@mdubakov This is really exciting news and will make things a lot easier for teams with users who have different requirements.
I think I saw somewhere that one of the next steps might be to use state or other fields to decide which view to show. That would make this even more useful. However, while this makes things nicer for multi-user workflows, it still doesn’t address situations where depending on the current users choices, the creator wants to display different fields, unless the user refreshes the screen so they can be sent to another view. That is why, I wanted to again pitch the possibility to control some fields (or group of fields) using based on conditions: