User accounts give programs the ability to grant and prevent system access. Each account contains a user's personal and system-related information, such as a user ID and email address.


All user accounts are initially assigned to the lowest-level parent organization in which they are created. This organization defines the data that he or she can view and manage. Each user account is associated with a user role(s) and a set of permissions.

A user can access data only for their assigned organization(s) and organizations lower in the hierarchy. 

 For example, if a user account belongs to a...
  • School - The user can access only that school data.
  • District - The user can access district data, as well as data from the schools assigned to that district.

PearsonAccess Training versus Operational Site

User accounts use same login and password for both the training and operational sites. However, organization assignments apply only to the site in which the account was created.

An authorized user must assign the user account to an organization in the alternative site — even for organization access identical to that of the other site.

 For example...

State Customer has an operational site and a training site. An administrator in State Customer creates a user account for Teacher User in the operational site and assigns that account to the Local School organization. Even though the Teacher User account automatically exists in the shared login system, Teacher User can use the organization assignment only in the operational site.

Why? Because the two sites contain different data, stored in isolated locations, and Teacher User has not yet been assigned to an organization in the training site.

To grant organization access to the user account on both sites:

  1. Create and set up an account in one site.
  2. Log in to the other site.
  3. Type the user account name into the search field, and click Search.
  4. Type/select the rest of the user account data on the second site.

Data in the shared login system includes username, password, and related account metadata (such the last account access date and whether the account is active). This metadata  is not site-specific. the The shared login system stores metadata updates from both sites. For example, regardless of which site you most recently visited, the time and date of that log in appears the same. 

Other details are site-specific, such as the role and permissions assigned to the user account.