When a Flow runs a skill that updates a ticket, the action is attributed to the flow creator rather than the Thread API member. The partner would like the ability to configure flows (or skills) to run as the Thread API member instead. It is unclear whether this change needs to be implemented at the flow level or the skill level, so both should be considered. This would improve ticket attribution accuracy and avoid actions appearing under a specific user's name.