To build a hierarchical view within a single application (like a "Manager" field in the Contacts application that points back to another record in the Contacts application), Archer utilizes Internal References . As taught in the Archer Administration II Advanced Search module, when an application references itself, you can use Directional Search logic to traverse the hierarchy.
By configuring the search to look "Upstream" or "Downstream" through the internal reference, Archer can recursively find all subordinates under a manager or all managers above an employee. This allows the system to flatten a complex organizational tree into a readable report. External References (Option B) are used between different applications, and Statistical Search (Option D) is used for mathematical aggregations (Sum, Count, Average). Only the combination of Internal References and Directional Search provides the specialized recursive logic required to map out a multi-level organizational hierarchy.

The manual Data Import tool has specific structural limitations compared to the more robust Data Feed Manager. As taught in Archer Administration II , Data Imports are designed to handle standard Applications and their associated Sub-Forms .
When importing into an application that contains a sub-form, the administrator can map source columns to the sub-form fields to create multiple sub-form line items for a single parent record. However, Questionnaires (Option A, B, and D) cannot be populated via the standard Data Import tool. Questionnaires utilize a unique
"Target/Assessment" architecture that requires either manual launching via a Campaign or the use of the Data Feed Manager with a specialized "Questionnaire" transporter. Because the Data Import tool lacks the ability to handle the complex relationship between the Question Library, the Questionnaire Template, and the Target record, it is restricted to standard application and sub-form data ingestion.

In the Archer security hierarchy, Access Roles are the primary mechanism used to grant functional access to an application. According to the Archer Administration II curriculum, an Access Role defines "what" a user can do (Create, Read, Update, Delete) within a specific application. While Groups (Option B) are used to organize users, a group itself does not grant permissions until that group is linked to an Access Role.
Record Permission Fields (Option D) are used for "Record-Level Security"-narrowing down which specific records a user can see-but they cannot grant access to the application itself if the user doesn't first have an Access Role granting them entry. DDEs (Option C) are used for UI automation and cannot manage security permissions. Therefore, to provide a user with the ability to see an application icon in their workspace and interact with its data, an administrator must assign them to an Access Role that has the "Read" right (and potentially others) selected for that specific application module.

The Data Import tool is designed for strict adherence to application business rules. According to the Archer Administration II curriculum, required fields are mandatory for the creation of any record. If a source file contains even a single row that is missing data for a "Required" field, the validation engine will trigger an error.
Unlike the Data Feed Manager , which can be configured to "Skip" errors and continue, a standard Data Import is an "all or nothing" operation by default when it encounters critical structural failures like missing required data. The import process will stop, and no records from that file will be committed to the database.
This ensures that the application does not end up with "broken" records that bypass the logic intended by the administrator. To fix this, the administrator must either populate the missing data in the source file or temporarily make the field "Not Required" in the application builder before re-attempting the import.

In the Manage Users section of Archer, the platform uses global defaults to ensure that new accounts are created with a baseline security posture. According to the Archer Administration II security module, every new user record is automatically assigned the Default Security Parameter and the Default Access Role defined in the instance settings.
The Security Parameter (Option D) governs password complexity, expiration, and session timeouts. The Default Access Role typically provides very limited "Read" access to ensure the user can at least log in to the workspace, but usually requires further administrative adjustment to grant functional permissions. A Username (Option A) must be manually entered or mapped from LDAP; Archer cannot guess a unique username. Similarly, email addresses and passwords require specific input or integration triggers. By automatically assigning the default Security Parameter and Access Role, Archer ensures that no user is created without essential security governance already in place.