Why it matters
The information needed to justify a masking exception is often different from what's needed to justify general data access. Having a single shared form meant stewards had to compromise on the questions they asked, or users faced irrelevant questions when submitting a request.
This change also brings data products in line with data assets, which have long supported separate forms. The experience is now consistent regardless of whether you're working with data assets or data products.
🔎 Learn more about data product and asset request forms in the documentation.