Currently both posture checks and MFA flows use a separate endpoint to handle object-to-location assignment operation.
This leads to an UX inconsistency, because a change is made without clicking Save in the location form.
Even if the user chooses to not Save the form, if they have touched the assignments a change has already been persisted in the DB.
We should instead add the postures and flows as nested objects in the request and store everything atomically on Save.
Currently both posture checks and MFA flows use a separate endpoint to handle object-to-location assignment operation.
This leads to an UX inconsistency, because a change is made without clicking Save in the location form.
Even if the user chooses to not Save the form, if they have touched the assignments a change has already been persisted in the DB.
We should instead add the postures and flows as nested objects in the request and store everything atomically on Save.