Retool Access Issues when updating workflow name or moving it to different folders

Hi there,
I am have recently started building a retool within my org. I have the exact same access as everyone in my org except for admin and the issues I will describe below are only for me despite having equal access. I would appreciate any help as to how to resolve this or if this is a bug.

  1. I create my own workflow, but when I rename it I receive an error. "Error saving workflow. You do not have edit and/or resource permissions required to update this workflow." My admin checked and there is no difference in my access
  2. I want to move my workflow to another folder, but when I try to it tells me "Failed to move workflow. Owner access to this workflow is required."

What is going on here?

Contact Retool support

Hey @mattyice, welcome to the Retool Community!

To rename or move a workflow in Retool, you’ll need either Edit or Own permissions. These are managed through permission groups, which control access to apps, resources, and workflows.

Edit Permission

  • Allows you to rename a workflow and update its configuration, including moving it to a different folder.

Own Permission

  • Grants full control over the workflow, including editing, renaming, moving, and deleting.

Please check what permissions you currently have for the workflow.

You can learn more about permission groups in the Retool documentation:
:link: Configure permission controls | Retool Docs.

4 Likes

I'm also getting this error. It only happens when editing the workflow's name. All the other changes within the same workflow are properly auto saved.

Hi @mattyice and @Tales_Rodrigues,

That is very odd and sounds like a bug. I am not sure how much I can help to debug since I can't reproduce this behavior on my end.

Let me check with the workflows team to see if there were any changes made to how to our permission system that could have caused these bugs :saluting_face:

@mattyice if you make any other changes to the workflow first, save those successfully then try to change the name does it still give you that error? And none of the other users on your org are having this error?

Hi folks,

Is this issue still persistent? Does it occur with newly created workflows where you have ownership permissions?