Create or modify a security role
Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
If the security roles that are provided with Microsoft Dynamics AX do not meet the needs of your business, you can create new roles. You can create a custom role that is based on an existing role, or you can build a completely new role.
Work with managers who oversee the different groups in your business to determine the appropriate permission levels for roles. For example, work with a manager in the Finance department to determine permission levels for Finance roles.
Only the Microsoft Dynamics AX administrator can create or modify a role.
Viktig
Be aware that modifying roles may affect your licensing requirements. For more information about how licensing relates to security, see the Security roles and licensing white paper for Microsoft Dynamics AX 2012.
Click System administration > Setup > Security > Security roles.
To create a new role, click New. To modify an existing role, select the role.
If you are creating a new role, enter the name that you want to appear for the role in the Application Object Tree (AOT).
Obs!
AOT names must contain only alphanumeric or underscore characters. AOT names cannot begin with a number, and they cannot contain special characters or spaces.
Enter or modify the display name of the role.
Enter or modify the description of the role.
To add security privileges to the selected role, click Add... to open the Add privileges to role form.
Find the security privileges that you want to add. You can sort and view the privileges by role, process cycle, or duty/privilege. You can also enter a privilege name or keywords in the Find field.
Tips
Security is organized hierarchically. Permissions on specific application elements are combined into privileges, privileges are combined into duties, and duties are grouped into process cycles. You can assign either duties or privileges to roles. For more information about the security hierarchy, see Security architecture.
To include all of the permissions from another role, open the Security roles form, and drag the role that has the permissions that you want to the role that you are modifying. By dragging one role to another, you create a hierarchical relationship, where the main role contains all of the permissions of the sub-role. If you change the permissions of a sub-role, the changes also apply to the main role.
A role cannot contain duties that conflict according to the rules for the segregation of duties. For more information, see Set up segregation of duties.
To remove a duty, privilege, or sub-role from the role, select the duty, privilege, or sub-role, and then click Remove.
To change the role’s permission level on securable objects such as controls, tables, fields, and server methods, right-click the role, and then click Override permissions.
Obs!
Overrides for securable objects are not associated with specific duties or privileges. If you apply an override, the access level for the securable object is set for the role, regardless of access levels specified by the duties and privileges assigned to that role.
To limit access to rows, or records, in the database based on a query, you can use record-level security. To apply filters for record-level security, right-click the role, and then click Record-level security. For more information, see Manage record level security.
Viktig
The record-level security feature will become obsolete in a future release. If you are setting up new filters, we recommend that you create data security policies by using the extensible data security framework.
When you have finished modifying the role, click Close in the Security roles form.