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. HierarchyAll 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.
PearsonAccess Training versus Operational SiteUser 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.
To grant organization access to the user account on both sites:
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. |