For a longer time, I was considering documenting several experiences how to setup specific security topics in Microsoft Dynamics 365 Finance and Operations and Microsoft Dynamics AX 2012. Since I started implementing Damgaard Axapta 2.5 in 2001, I have done a lot of security setup and had sometimes some complex challenges. This post will be a table of contents for all documented scenarios and will be updated when a new blog post in this series will be published.


Some security scenarios are quite common in implementations, but require some setup which is a bit different from just the basic artifacts as security roles, duties and privileges. In the scenario’s I will try to provide as much as possible details if there are different approaches for Dynamics 365 versus AX 2012.

I have a backlog of several scenarios, like how to restrict a purchaser from viewing details of claimed expenses if workers are setup as vendor or how to prevent someone to be able to approve his own timesheet.

If you have some scenarios where you need help or just want to know how I would solve it, please leave a comment at the bottom of this post or send a message via the contact form. I will review the request and will add it to the backlog.


In the table below, you will find links to the documented scenarios. Note that there might be more options to solve a certain scenario.

Date publishedScenario description
2020, August 31 A purchasing agent is not allowed to view employee expense transactions
2020, November 8A purchasing agent is not allowed to maintain vendor bank details
2020, December 8Only a finance user is allowed to change the on-hold status of vendors and customers – Dynamicspedia

New scenarios will be added in the coming period. You may come back regularly visiting this page to read how to secure different scenarios.

I do hope you liked this post and will add value for you in your daily work as a professional. If you have related questions or feedback, don’t hesitate to use the Comment feature below.

That’s all for now. Till next time!

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.