|
|
|
Logical domains enable communities of users and some content to be partitioned within a single instance of PeopleFluent Learning. Domain-specific content includes email templates, enrollment policies, repository files, courses, catalogs, and user groups.
Logical domains define a number of properties, common to all users in a domain. These include the default System Administrator user, default new user profile, skin and primary language.
The LMS ships with the Global Default logical domain, to which all users belong until they are assigned to an alternative domain.
Domains have a one-to-one relationship with organizations: only one organization can be assigned to a domain, and different domains cannot be assigned the same organization.
System administrators can:
You can create new logical domains only if the Multiple Assignments feature is disabled in System Configuration. Multiple Assignments allows users to have multiple jobs, organizations, roles and other assignment details. (Likewise, multiple assignments can be enabled only if there is one logical domain; these two features are mutually exclusive.)
Deleting a logical domain re-assigns its users, and its domain-specific content, to the Global Default domain.
User administrators who are not in the Global Domain can upload user data via the User Data Loader only to their client domain.
When administrators who are not in the Global Domain create new users in the User Editor or via the User Data Loader, the new user's organization defaults to that of the administrator; their language and skin default to those assigned to the domain the organization is assigned to. New users can be assigned to other organizations (and therefore domains) but their language and skin must be updated manually.
To manage logical domains, go to Manage Center > System > Logical Domains.
The main reason to have separate logical domains is to ensure that users in one domain do not see users in a different domain. Users in the Global Default domain may see all other organizations and users in the LMS, constrained only by permissions settings. Separate client domains, however, are automatically restricted to user management within that domain, and by default cannot see or be seen by users in other client domains. In most pages where users are displayed or selected, the list is restricted to same domain membership.
When creating logical domains, you can choose, separately, whether users in a logical domain can see users and email templates from other domains.
If creating separate login or and logoff pages for each domain, you must also plan for how you want users from different domains to get to that specific login page (for example, via a portal, a unique domain name, or using JavaScript handling).
Permissions control is still in effect throughout the LMS, and is applied in addition to domain filtering. For example, within a domain you can still use permissions to limit which items and departments are accessible to other users within the domain.
New child organization units are automatically assigned to the logical domain of their parent organization. New users are automatically assigned the domain of the organizational unit they belong to.
Moving an organization unit to another parent organization unit removes it from its original domain and reassigns it to the domain of its new parent. Child-organizations and users are re-tagged automatically. Content (such as email templates) is not automatically re-tagged, although deleting a domain will cause all items to be reassigned to the Global Default domain.
Additional Information
