CHAPTER 1: ARCHITECTURE
CHAPTER 2 : DATA DICTIONARY
CHAPTER 3 : USER INTERFACES
CHAPTER 4 : SECURITY
Lesson 1 :Introduction and Objectives
Introduction and Objectives for Security in AX 2012 R3:
Introduction and Objectives for Security in AX 2012 R3 explains Role based security provides an extensible framework for defining access to the Microsoft Dynamics AX application and data. A security role relates to a job role that an end-user has within an organization. The role includes duties, privileges and permissions required to perform the tasks required in that role.
The maintenance of roles and duties is typically undertaken by the system administrator in the rich client. The maintenance of privileges and permissions is typically undertaken by a developer in the developer workspace. The framework and related tools assist the security administrator to ensure the system is secure.
The objectives are:
- Describe the elements of Role Based Security in Microsoft Dynamics
- Setup a new user.
- Assign roles to a user.
- Assign a security role to a user.
- Edit duties assigned to a role.
- Edit privileges assigned to a duty.
- Edit permissions assigned to a privilege.
- Search for roles with access to a menu item.
Establishing security for your Dynamics AX users can be a daunting experience if you do not fully understand how security is built in Dynamics AX. Understanding the security architecture in Dynamics AX will help make security setup for your organization much more straight forward and simple. Once you understand the building blocks of security in AX, your organization can determine a process for configuring security to meet your needs.
The first thing to understand about AX security is that although AX comes with predetermined security roles, out of the box, security roles can always be customized or even built from scratch to meet your needs. AX security is setup as a hierarchy, the top level of AX security is a security role. A security role is an overall title for the security access that a certain type of employee would have. For example, out of the box, AX has roles for AP Supervisor or Chief Financial Officer, keep in mind you can also build a new role from scratch, for example we have seen clients build an AP Specialist role. All security roles are comprised of duties and privileges, which will be further explained below.
When building a custom role, or when adding duties and privileges to roles a hierarchy is used to help you find the duties or privileges you need. The top level of this hierarchy is a process cycle. A process cycle defines a set of activities included in a certain business process. An example of a process cycle would be Revenue Cycle. Within the process cycles there are duties. An example of a duty would be approve customer invoices. Within duties there are privileges. An example of a privilege would be approve customer journals.