Redwood VBS Deployment Strategy in Production – Multi Vendor Environment Clarification

Summary:

We are implementing Redwood custom validations in Oracle Fusion HCM using Visual Builder Studio (VBS).
In the TEST environment, our team created a separate VBS project for implementing Redwood validations (Absence module – Sick Leave related changes).
However, the client has multiple vendors. who are also working on Redwood customizations.
Before migrating to Production, we need clarification on the deployment governance model:
Is it recommended that all vendors use a single common VBS project for Production?
Is there any Oracle recommended best practice for managing Redwood changes in a multi-vendor environment?
Our objective is to ensure that no previously deployed Redwood validations are lost or overwritten.