The essential tasks to be performed when linking data view and organization view at the design specification level are to define the responsibilities of organizational units for company data objects and to determine the access privileges that essentially define which organizational units may access specific company data.

The relationships thus established link technical objects of the organization view (organizational unit, position, role, person, etc.) with data objects of the relations diagram at the design specification level (relation, attribute, view). Therefore, these relationships are attributed to the process view's design specification level.

In order to define access privileges for relations or individual fields, the relevant data objects can be assigned either positions or roles. This allows you to stipulate that a certain position is authorized to access particular fields, but by assigning roles, you can also define business rules such as this field may only be accessed by department heads. The following figure illustrates an example.

Defining the responsibilities for the contents of a field or an entire relation is as important as assigning access privilege. For this reason, a second connection called is responsible for can be drawn between organizational units and data objects in the relations diagram. Unlike access privileges, responsibilities for data objects are mostly assigned to one position in the company only. Business rules similar to the ones mentioned earlier can again be defined by assigning roles. These rules then relate to the responsibility for a data object.

The following figure illustrates an example.