overriding shared field 'required' at local level

We have a shared date field which in one particular content editor it would be better if that field were optional.

From our initial Rx training I can’t remember whether it was ok to do this. I seem to remember something about if it’s optional globally it’s ok to make it required locally but not the other way about.

Am I remembering correctly or not?

Like you say, it is ok to make an optional shared field required locally, but I seem to remember tech support strongly advising me not to do it the other way round.

I guess it depends on the reason you’ve made the field required in the first place…