Page tree

Search the PearsonAccess Next Online User Guide:

Skip to end of metadata
Go to start of metadata

An organization is an entity in a customer's organizational hierarchy. For example, a state, a district, and a school are organizations. An organization must exist in the system before that organization can participate in testing or test-related activities.

The organizational hierarchy provides a backbone or a framework that gives structure to the data that will be stored in the system. For example, all students, administrators, and teachers in the system must “belong” to an organization. Only after the organizational hierarchy is built can student data and user accounts be uploaded. For this reason, building the organizational hierarchy is one of the first tasks.

The hierarchy of categories for organizations is created based on the defined requirements for your testing program. Your organization hierarchy will be unique to your program.

Here is an example: 

State Department of Education

          |_ District 1

                    |_ School 1

                    |_ School 2

                    |_ School 3

          |_ District 2

                    |_ School 1

                    |_ School 2

                    |_ School 3

Your program can only have one hierarchy that must be used by all organizations.

Your organization hierarchy will determine availability of different features and functionality of the system at different levels. After the organizational hierarchy is defined, you can upload your program specific data. Typically, you can only view data for your organization and organizations below it (child organizations).

This section describes the process of entering and managing specific details about organizations. 

Related Information

Enrollment counts are used primarily for ordering paper testing materials, such as test booklets or large-print and braille, as described in Manage Enrollment Counts.

You can view organization details by viewing additional information, as described in Understand the System Layout.

You can learn more about tasks and how to perform tasks by viewing additional information, as described in Perform Tasks.


  • No labels