Flowchart: Configuring the Administration module
Dynamics AX 4.0
The module contains forms for administrators to use to enable or disable features and functionality in Microsoft Dynamics AX. For example, the module contains forms for setting up Microsoft Dynamics AX users, groups, company accounts, and security. The module also contains data import and export forms, a license form, a configuration form, Enterprise Portal set up forms, and advanced reporting forms, to name only a few.
Install Microsoft Dynamics AX software.
Complete the Installation checklist. The forms used during installation are described in more detail in the following topics:
The forms that a company must set up to be able to use the basic functionality of the module are listed in the recommended order of setup.
 Important |
|---|
If these forms are not set up and configured properly, features or functionality may not be available to end users, or users may not be able to access Microsoft Dynamics AX.
|
1. Users
Enter details about each user who will access Microsoft Dynamics AX in the form. To add an additional layer of security to your computing environment, Microsoft Dynamics AX requires that all users be listed in Microsoft Active Directory directory service on your domain controller before they can be enabled in the form. If a user is not enabled on this form, that user cannot access Microsoft Dynamics AX.
For more information, see Active Directory user topology and User (Form).
2. User groups
, see User groups (Form).
By creating users groups, you establish who can access Microsoft Dynamics AX and what permissions users have when working in the product. By adding a user to a group, you give the user all the permissions and user rights assigned to that group. Before users can access Microsoft Dynamics AX, they must be added to the list of users and they must be added to at least one user group.
3. User group permissions
Permissions determine who can access menus, forms, reports, and tables. In Microsoft Dynamics AX, you assign permissions to user groups instead of individual users in the form. Assigning permissions to groups saves time because you do not have to adjust permissions for each user.
When you create a new user group in Microsoft Dynamics AX, the group, by default, is set to No access for all menus, forms, reports, and tables. This means that after you create a new group, you must use the procedure in Set up security keys to enable permissions; otherwise all members of the group are denied access to all menus, forms, reports, and tables.
For complete guidelines, see User group permissions (Form).
The setup of the module includes a number of other steps beyond the basic functionality.
The additional setup forms are organized by functionality.
Record level security
Record-level security builds on the restrictions enforced by user-group permissions in the form. With user-group permissions, you restrict which menus, forms, and reports that members of a group can access. Record-level security enables you to restrict the information shown in reports and in forms.
For complete guidelines, see Record Level Security (Form).
Domains
If your organization or business has more than one company account, you can restrict account access using domains in the form. Domains restrict account access in the same way user groups restrict user access. With the combination of domains and user groups, you can create a strict security policy where each user group in each domain is a distinct entity with absolutely no access between groups/domains. Or you can create a customized security policy where, for example, one group has account access to similar group data, forms, and modules across multiple domains.
For complete guidelines, see Domains (Form).
Virtual company accounts
Virtual company accounts contain data that is shared by more than one company account and are set up in the form. Real company accounts that belong to the same virtual company account create and manage data in the same database. Virtual company accounts are usually used with a limited number of tables.
For complete guidelines, see Virtual company accounts (Form).
Database log
For complete guidelines, see Database log (Form).
E-mail parameters
For complete guidelines, see E-mail parameters (Form).
No comments:
Post a Comment