@shreyak.garg We too are facing the same issue. Just to further shortlist the two differences between you and the user - in our case both the user and the WA have SSO enabled. So, essentially, everything else being equal - being WA seems to resolve this issue.
Please do update this thread in case you happen to find the cause/solution.
@shreyak.gargIf I'm understanding you correctly; you have a numbered list with selective access enabled. There are also orphans in the numbered list. The action which is causing errors is mapping parents to these orphans.
Anaplan correctly denies access to orphans in a list with selective access enabled to non-WSA users. This is why the action is causing the error.
I suggest either mapping the parent in the same action that is currently creating the orphans. Or alternatively, the orphans being created currently should be mapped to a temporary dummy parent. This will allow all users access to the orphans and the last action should successfully remap the 'orphan' to the desired parent
Is it possible that the user running the action does not have access to the parent that the child is currently at.
The user I'm testing with does not have access to P3, the parent of C6 and is also not a WSA
When this user runs an action to update the parent of C6 as below he will receive the "Unauthorized to move this entity" error
The difference between my original answer and this is that the problem child is not because it is an orphan but because it is currently mapped to a parent which the user cannot access. When the user tries to remap any child to any other parent, irrespective of whether he has access to the destination parent, he will be unauthorized to make the change.