Hi!
We are experimenting with the new “My Work” functionality, loving it so far! We have however encountered that the tasks doesn’t inherit the permission level of the workflow. We are able to see tasks that are connected to a workflow with “No access”, although we can’t see the actual workflow run or the tasks configured within the workflow, the additional tasks are visible.
Hi Daniel thanks for getting in touch about this. Can you tell me if those attached tasks are assigned to users or not? If you’re able to make a quick screen recording for us that would be really helpful, thanks
They are attached to users. So I can see the tasks through the “My work” by either selecting them as user or a group that said user is part of. I’ll try to record later. Since I am admin, it’s hard to demonstrate, but I have tested it with other members as well.
So for example to test it, I set up a new private workflow (that should only be visible to me) with only one task which is given “no access”. To this workflow, I can then attach stand-alone tasks, that are by default assigned to myself upon creation.
Other people can then see my task, in my private workflow, by choosing my name in the “My Work” tab (or a group that I am part of). If they attempt to go to my workflow though, they are redirected to the Library.
Glad to hear you’re getting a lot of value out of My Work!
Attached task don’t inherit the permissions from the run. This was an intentional decision to allow users to attach tasks to run for someone to do without having to give access to that run.
That being said, we could improve the user experience and disable the link to the run to make it clear they don’t have access to the run. I’ll pass that on to the team.