Help meez continue to create great products!


At meez we're on a mission to revolutionize the way you work in kitchens around the world, and we need your help. If you have ideas about how we can improve our platform, add new functionality, or solve challenges that you face in the kitchen, we'd love to hear from you. Please submit your idea(s) below for our product team to consider with future releases.

Before submitting your feedback, please use the search field to check if a similar idea has already been submitted and vote for the existing idea rather than duplicate the request. More votes equal a higher priority on our product roadmap.

Note: Your submission will not be visible in our portal until it has been reviewed by our Product team.

Thanks for taking the time to share your feedback! We appreciate it.


- the meez product team

Add a new idea Subscribe
Status Accepted
Created by Gabe Ross
Created on Dec 8, 2022

RELATED IDEAS

Sub-recipe ownership (concept assignment) should not be locked

Currently, sub-recipes inherit their parent recipe ownership (concept assignment), which is good. But as long as the sub-recipe is used in any other recipes, there is no way to edit those permissions. For example, if I wanted to add the sub recipe to another concept where it is not yet used.

Additionally, once the sub-recipe has been assigned to a concept, it never leaves - even if the parent recipe in that concept is deleted or the sub-recipe is removed from the parent recipe. Since the ownership permissions are locked, there is no way to remove a sub recipe from a concept unless you make it NOT a sub recipe by removing it from all parent recipes where it appears.

  • Attach files