Required dependent brand properties prevent other teams from updating the main brand property

Hi everyone,

I’m seeing an issue where required properties + conditional field visibility prevent users from other teams from updating our main brand property.

We use conditional fields that appear when a specific brand is selected. Some of these dependent fields are marked as required and only editable by the team that owns that brand.

What happens:

  1. Users cannot select a brand if its dependent required fields belong to another team (they don’t have permission to edit them).
  2. Users also cannot change the brand away from that value if the required fields were never filled in — changing the brand re-triggers the requirement.
  3. Inline edits bypass required fields, but this is not a reliable solution.

As a result, the brand property becomes effectively locked for users outside the brand’s team.

My question:

Is this expected behaviour, or a limitation in how required properties interact with permissions and conditional fields?
And is there a recommended best practice or future improvement for this scenario?

Thanks!