Introduction to Microsoft Dynamics AX 2012 R3 Development-1

Microsoft Dynamics AX 2012 R3 Development-1

Locus IT ServicesMicrosoft Dynamics AX 2012 R3 Development-1

Lesson 2 : Setup a new user

Set Up a New User:

This section describes security concepts to set up a new user,and explains how to set up and maintain security in Microsoft Dynamics AX. The following topics are included:

  • Security architecture of the Microsoft Dynamics AX application : When you understand the security architecture of Microsoft Dynamics AX, you can more easily customize security to fit the needs of your business. By default, only authenticated users who have user rights in Microsoft Dynamics AX can establish a connection.The Microsoft Dynamics AX client uses integrated Windows authentication to authenticate Active Directory users. Enterprise Portal supports flexible authentication, which allows you to use authentication providers other than Active Directory. If you configure Enterprise Portal to use a different authentication provider, users are authenticated by that provider. After a user connects to the client or Enterprise Portal, access is determined by the duties and privileges that are assigned to the security roles that the user belongs to.
  • Role-based security in Microsoft Dynamics AX : In role-based security, access is not granted to individual users, only to security roles. Users are assigned to roles. A user who is assigned to a security role has access to the set of privileges that is associated with that role. A user who is not assigned to any role has no privileges.In Microsoft Dynamics AX, role-based security is aligned with the structure of the business. Users are assigned to security roles based on their responsibilities in the organization and their participation in business processes. The administrator grants access to the duties that users in a role perform, not to the program elements that users must use. Because rules can be set up for automatic role assignment, the administrator does not have to be involved every time that a user’s responsibilities change. After security roles and rules have been set up, business managers can control day-to-day user access based on business data.
  • Data security in Microsoft Dynamics AX : This part of the documentation describes how to help secure data in Microsoft Dynamics AX this sections are included: Manage record level security Manage data access by using the Table Permissions Framework
  • Best practices for upgrading to role-based security : This topic provides an overview of some best practices that you should consider when you upgrade security. This topic does not describe how to upgrade security settings to Microsoft Dynamics AX 2012. For information about how to upgrade security settings. When you convert user groups to roles, we recommend that you use the default roles as much as you can. The default roles that are included with Microsoft Dynamics AX 2012 may contain additional permissions that were not available in earlier versions of Microsoft Dynamics AX.

Users are setup in the rich client. They are typically imported from Active Directory. A user is assigned multiple roles. An internal user is assigned the following two roles in addition to functional roles:

  • The System user role provides access to basic functionality and tools so that a user can access and use base functions in Microsoft Dynamics AX.
  • The Employee role provides access to base functionality that all internal roles can use. This includes employee self-service on the Enterprise Portal.
Locus IT Project Management Office
What’s it?