Removing the reassign function from workflows in D356FO

(1) Share

Report

Posted on by JF-11061402-0

Workflows can be reassigned seemingly unrestricted and this could lead to compliance issues.

Is there a solution to restricting or removing the reassign button in Workflow History, therefore preventing users from being able to reassign, or restricting this function to a specific set of users/user roles

Categories:

Dynamics 365 Finance

I have the same question (1)

All responses (4)

Answers (3)

Verified answer

Sohaib Cheema 49,438 User Group Leader on at

Like (0)

Report

System Admin can re-assign, so remove that security role from unwanted people.

Further, for every workflow there are menu items on the backend. Those menu item provide you access to (Approve, Reject , Cancel, Delegate etc.). Delegate does the same as Re-Assign.

If you want to remove the Delegate as well, you should watch

1) Is standard security assigned? >> Find the privilege/Duty that is granting this access, Create a copy of it and remove the Delegate menu item.

2) If custom security role being used? >> Remove the menu item that is providing access to the delegate button.

1 people found this reply helpful.

Was this reply helpful? Yes No
Verified answer

André Arnaud de Cal... 300,917 Super User 2025 Season 2 on at

Like (0)

Report

Hi JF-11061402-0,

Can you update us on the status of your question? Have you been able to find your answer?

Note that Sohaib is correct about permissions. Out of the box, this option is only available to system administrators and users with the Information Technology Manager role. In case you have custom security, it could be added to other persons as well.

In addition, there shouldn't be a compliance issue. When someone has the permission to perform a reassignment, then this will be logged in the history. Also, to be able to use the Approve option, a user should have the permission via security roles to perform this task for the workflow type.

You can read more about workflow security on my blog: Workflow security in Dynamics 365 Finance and Operations - Dynamicspedia

1 people found this reply helpful.

Was this reply helpful? Yes No
JF-11061402-0 20 on at

Like (0)

Report

Hi Shoaib, Andre.

Thanks very much for the information. I’m clear on how to restrict the reassign function. It seems whatever action we take to restrict Reassign, we should also do for Delegate. We will have a small group of users who will control both functions to ensure our workflows are not bypassing the LCOA without the correct authorisation.

If you have any final advice on restricting access to the delegate function (I know Shoaib already mentioned it), that’d be greatly appreciated. If not, then I will mark this question as answered.

Thanks

Was this reply helpful? Yes No
Verified answer

Sohaib Cheema 49,438 User Group Leader on at

Like (2)

Report

Hi @JF-11061402-0

Delegate is controlled by it's action menu item. For standard workflows it has corresponding permission (privilege) which is usually tied along with other actions in a duty. Other action could be Approve, Reject etc

You may end up creating two duties, one which provides approval/rejection actions and keeping the Delegate in a separate duty.

Look at the example of Duty named as LedgerLedgerTransactionsApprove

it is keeping the approval/rejection with the Delegates.

If you are talking about a custom workflow that depends how you workflow's security is developed.

1 people found this reply helpful.

Was this reply helpful? Yes No