CHAPTER 1: ARCHITECTURE
CHAPTER 2 : DATA DICTIONARY
CHAPTER 3 : USER INTERFACES
CHAPTER 4 : SECURITY
Lesson 6 : Assign a Permission to a Privilege
The assignment of permissions to privileges is typically maintained by a developer in the AOT; however this can also be maintained by a system administrator in the Security privileges form in the rich client.
Menu items and web content items can be dragged-and-dropped onto the entry point node on a privilege in the AOT. The permission level is set on the properties.
In assignment of permissions to privileges we will discuss roles, duties and privileges in Microsoft Dynamics AX 2012. These security levels cover access to single elements, forms, and groups of elements needed to perform a duty. A developer is responsible for defining more granular security levels by setting access on tables and controls in a form, or by associating classes that perform an action with permission.
A privilege is a group of permissions. The nodes that are underneath each privilege node identify the securable objects that a user can access. And those nodes set the level of access for each object.
This section describes the best practice rules for privileges.
- You can use privileges to specify the access that is required to accomplish a job.
- You can use privileges to group together the permissions for related securable objects. For example, menu items and their controls are closely related.
- You can assign privileges directly to security roles. However, security settings are easier to maintain if you assign duties or process cycles instead of privileges.
This section describes the properties for the AOT node at Security > Privileges > YourPrivilege.
|Name||Yes||Name of the privilege.|
|Label||Yes||Text that appears on the user interface for the privilege.|
|Description||Yes||Description of the privilege.|
|Enabled||Yes||The enable value. The value can be one of the following: