So after doing some research it looks like the approval options are hardcoded into the product. HOWEVER…it would be great to be able to customize those options based on different worflows. I won’t go into every example but a good once that transcends all of our creative workflows would be to add an “approved with changes” option. This would give the team the clarity and confidence to make the changes and move forward.
NOW I know I could make a custom field but honestly it feels like a band aid in this case (you can only make so many custom fields). It would be great to simplify and add the ability to change and or add names and approval phases to that function. Thanks so much ( this really isnt much of a question but more of a request for the dev team)
You can actually make your own approval type as you’d like the options to be by using the Asana custom task types feature (much better for this purpose than custom fields). In addition, these are available in all paid plans, not just Advanced and up.
More info: Asana Help Center
Thanks,
Larry
Thanks @lpb !!! I appreciate the insight and I have used that in the past for other things. However I explicitly want the ability to change the approval function not just custom fields. I would like some of these things to be built in and not just be band aids for solutions if that makes sense.
sorry not just custom task types**
Respectfully, and for the benefit of others reading, I think my characterization of the custom task types feature might be more objectively fair than yours 
There’s probably a English Forum > Product Feedback request you could search for and vote on. (But my personal take is that I would bet Asana will not be modifying that existing feature for a number of reasons.)
Thanks,
Larry
@lpb I’ve actually had some really decent discussions with the Asana Dev team about new features that should be rolling out over the next year, so they are definitely open to feedback and improvement. My comment definitely wasn’t meant to be combative toward you.
What I’m really getting at is something I’ve noticed within Asana itself. Sometimes functionality that should be part of the core feature ends up having a solution through another rule, custom field, or workaround. Those things are helpful, but I think they should be helpers and not something we have to use to make up for a limitation in the actual function.
I appreciate you pointing out the custom task types and I know that can accomplish something similar. I’m just specifically talking about having that flexibility built into the native Approval function itself.
Thanks again for the insight though. I do appreciate it.