Hey everyone
Been looking at the new Proofing tools that had been added a few months back. Its a decent start and I have been considering this as part of our workflows.
We typically work with a number of partners that submit updated images to us for review. The idea is we have a task with an image field that is formatted for Versioning.
When our partner has a new version of the image that they can submit that into the image field so the internal team can review and give feedback. This seems a little backwards for how the workflow was designed. I think the intent was that the partner would create this in their AirTable, we would be commentors on the images and they would update the images. Is that correct? Thats not great for us since we have dozens of partners and need to have those assets flowing into us to centralize the review process.
To make this work for us, I would need to have an Editor license for each partner that would be submitting image versions. Is that correct?
I also looked into using a form to create an update record in a separate table and then have an automation version the image into the main table. But it looks like automations do not support versioning. At least, I dont think it does.
Starting to suspect that this workflow is not something I can do without purchasing a lot of licenses.
Anyone else experiment with Proofing workflows?
Thanks!
M


