Security Integration with the Organization Model

In earlier versions, the company context (represented by the DataAreaId column
in tables) was always applied. This meant that tasks in Microsoft Dynamics AX
could be performed only in the context of a company. In addition, users could
access tables without a DataAreaId column only when they were logged on to a
company where they were granted access to those tables. If a user needed to
perform an action or access a table in a different company, that user was required
to log on to that different company.

In Microsoft Dynamics AX 2012 users can view or edit data in different
organizational structures, instead of the company they are logged on to. For
example, a user might enter records in Human Capital Management by using a
human resources organization hierarchy and enter financial transactions by using
a legal entity organization hierarchy. Data security filters take the hierarchical
structure into consideration. For example, you can set up a filter that applies to
the current organization and any organizations underneath it in the hierarchy.

IMPORTANT: Some tables in Microsoft Dynamics AX 2012 contain a
DataAreaId column. To help secure data in these tables, the administrator can
specify a company context for a particular user in a role.

NOTE: Before an organization hierarchy can be used for security it must be
given the security organization hierarchy purpose. 

Regards,
Hossein Karimi