Hey @KANHAIYAV . The logged in user is visible in Flows that run from the Playbook, but I'm really intrigued by your use case. You've posted this in the SPM Forum, so I'm guessing you're planning to use this Playbook on a Project or a Demand. Given that those are both services that require roles for access, it seems unlikely that you're trying to base behaviour on the users' roles, so I'm wondering, is the data you need something that's already getting captured on the project/demand form, like a business unit, department, assignment group? If so, that would be a much more robust way of building your logic.
