How to build the right architecture for updating the activity/invisibility statuses of form elements?

Question

Design patterns

In my IP there is a module in the form of a form with 10-12 elements (panels, comboboxes, buttons). This module is quite "low-level" - it is used as part of a dozen (or even more) other modules. Also, the IS has a wide tree of user rights, and there are various business logic requirements that can affect the activity / invisibility of buttons.
My task is to refactor the part of the form code responsible for the visibility / activity of the buttons, so that in the future it would be easy to maintain the code for adding new visibility requirements.
That is, the visibility / activity of buttons depends on the module containing my form, user rights (and on a combination of rights), business logic requirements. Moreover, any of the listed requirements can affect both one element and several at a time. At first glance, now each form element is affected by a combination of up to 15-20 requirements. I ask for advice and parting words, how can I implement the architecture for convenient addition of requirements, what design patterns should I look at and apply?