The users are having NON Workspace admin access, so when you are trying to run the process, then are facing "You are not authorised to move item to parent: <X>".Any suggestion to resolve this?
@CommunityMember126537
Probably the User Role that the users are defined is not having 'Write' access to that particular List on which they are trying the operation.
~Anand
Hi @anand.shekhawat - The user having access(write) to the module and list.
The user is not having the access to hierarchy as they are out of the hierarchy.Here, we are the user is trying to assign the code from his/her hierarchy to other hierarchy on which he/she is not having the access.For Example: There are two list A and B.The child of List A needs to be assign to List B, but the user is having access only to List A hierarchy.Could you suggest any solution?
If they are not having the access, how will they gonna do then? I think they need to have the access to perform the action.
Hi @CommunityMember126537 ,
This happens when the user does not have the selective access of the parent item to which you need to assign the child.
Refer to the link attached here for better understanding:https://community.anaplan.com/t5/Anaplan-Platform/You-are-not-authorised-to-move-this-entity/td-p/50059/page/2
Thanks!
This shows all comments across all data to all users with access to the UX page. This is not appropriate for any UX which might contain security access sensitive data. Comments on grids and cards ARE security dependent. That works fine. But anyone with access to the page can open this Summary Panel and see ALL comments…
If anyone is aware of idea exchange ideas that are currently being evaluated by the product team, if you don't mind linking them here, would love to give them an upvote. Thanks!
Hi, I’m experiencing a strange issue in ADO that I can’t seem to resolve. Before reaching out to Anaplan Support, I thought I would check with the community for advice. I’m trying to extract some list properties for an ADO mapping from a Polaris model/module. However, no matter what I do, I keep encountering the same error…