In AEM Communities, from the publish environment (depending on permissions configured), site visitors may become members, create user groups, and edit their member profile .
User data is a term used to refer to users, user profiles and user groups.
Members is a term used to refer to users registered in the publish environment, as opposed to users registered in the author environment.
For more information regarding user data, visit Managing Users and User Groups.
By design, user data created in the publish environment does not appear in the author environment.
Most user data created in the author environment is intended to remain in the author environment and is not synchronized nor replicated to publish instances.
When the topology is a publish farm, registration and modifications made on one publish instance need to be synchronized with other publish instances. Members need to be able to log in and see their data on any publish node.
When user synchronization is enabled, user data is automatically synchronized across the publish instances in the farm.
For detailed, step-by-step instructions, on how to enable synchronization across a publish farm, see
By design, users and profiles created in the publish environment (such as by self-registration, social-login, LDAP authentication) do not appear in the author environment.
When the topology is a publish farm and user sync has been correctly configured, the user and user profile is synchronized across the publish farm using Sling distribution.
Although initiated from a publish instance, the community group creation, which results in new site pages and a new user group, actually occurs on the author instance.
As part of the process, the new site pages are replicated to all publish instances. The dynamically created community user group and its membership are Sling distributed to all publish instances.
By design, user data created in the publish environment does not appear in the author environment and vice versa.
When the User Administration and Security console is used to add new users in the publish environment, user sync will synchronize the new users and their group membership to other publish instances, if necessary. User sync will also synchronize user groups created through the security console.
For user generated content (UGC), the data entered on a publish instance is accessed through the configured SRP.