Security Duty Properties

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

In Microsoft Dynamics AX, security permissions are combined into privileges, and privileges are combined into duties. Duties are defined as a group of related privileges that provide a user with access to a specific business function. In the application object tree (AOT), these privileges are organized into the nodes of a duty.

Best Practices

This section describes the best practice rules for duties.

• All duties should be assigned to a role.

• All duties should be part of a process cycle.

• Because a duty represents a specific business function the name of the duty should rarely or never change. For example, your company pays bills. The details of how you pay bills may change but the essential function of paying bills will not change. Instead of creating a new duty you should change the privilege subnodes of the duty.

• The name of a process cycle should rarely or never change.

AOT Duty Hierarchy

The following list shows the hierarchy of duty nodes in the AOT:

• Security

  • Duties

    • YourDuty

      • Privileges

Duty Properties

This section describes the properties for the AOT node at Security > Duties > YourDuty.

Privilege Properties

This section describes the properties for the AOT node at Security > Duties > YourDuty > Privileges > YourPrivilege.

See also

Role-based Security in the AOT for Developers

Role-Based Security System

Role-Based Security Concepts Overview

Announcements: New book: "Inside Microsoft Dynamics AX 2012 R3" now available. Get your copy at the MS Press Store.