Share
Report
96We are refactoring our custom security model in Visual Studio (AOT) to improve maintainability and avoid licensing escalation issues caused by overly broad privileges.
What are the recommended design patterns for structuring Privileges and Duties in D365 F&O? Specifically:
How granular should a single Privilege be (e.g., restricted to a single menu item/business task vs. full sub-module access)?
How do you prevent broad Privileges from inadvertently driving up user license SKU requirements (Operations vs. Activity/Team Members)?
What is the cleanest hierarchy for structuring custom Duties so they remain reusable across multiple custom Roles?
Categories:
I have the same question (0)
All responses (
Answers (
