Based on my current understanding, the only way to transfer ownership of an automation from one individual user to another is for the new owner to open the automation, make an edit, and save it—thereby taking over ownership in the process.
I noticed that there is a dedicated “Manage ownership” feature for transferring ownership to/from a third-party application (service user). Is there an equivalent mechanism for transferring ownership between individual users—one that reassigns only the owner field without requiring any changes to the automation’s condition, effects, or other configuration (e.g., an admin-level override, or an API-based operation)?
Our use case is reassigning ownership across multiple automations in bulk when responsibility shifts between team members due to role changes. If anyone is aware of such a feature or a recommended workaround, I’d greatly appreciate your input.
From my knowledge there is no method to reassign ownership in bulk, however going forward you could make use of the “Third-party application ownership”.
If you register a confidential client third-party application with client credentials grant enabled in Developer Console.
Grant the resulting service user appropriate permissions (editor role on automations, access to required actions/resources).
For each automation use the Actions → Manage ownership dropdown on each automation to transfer ownership to the service user by providing the client ID and client secret.
For each automation create/assign a group (with the relevant team members) as the automation administrators - as ‘All recipients’
This way you don’t have to worry about reassigning ownership between team members as the service user will always be the owner, you just need to add/remove users from the group so that the relevant people get notified
Thank you so much for the detailed explanation and the screenshots — this really clarified things for me. I’ll mark this as the solution. Really appreciate your help!
