Applicable Product:

• PeopleFluent Learning

Applicable Release:

• All versions

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 

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.

Tagging 

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 retagged 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.

System administrators with read-only or unrestricted access to the System Administration feature in System Roles (Manage Features > System Administration) can create logical domains.