Setting up Site Groups

Objective

After completing this lesson, you will be able to discover the benefits of Site Groups to deliver a streamlined branding experience for your customers.

Site Groups

Site Groups

Consider a company that maintains multiple websites or applications, each requiring user authentication. Managing separate logins for each platform can be frustrating for users.

The diagram below illustrates the single sites we have seen in previous units.

Diagram describing situation without Site Groups: Three user logins in to separate sites (Brand A, B, and C). Each brand site has their own Brand Identity DB.

Site Groups are designed for organizations that own multiple sites and want to provide users with a different experience on each site while maintaining a unified user database and centralized settings configuration. Key aspects of Site Groups include:

  • Unified User Database – All sites within a group share the same user database, ensuring a single source of truth for user information.
  • Centralized Configuration – Settings and policies can be configured centrally for the entire group, simplifying administration and ensuring consistency.
  • Customized Experiences – While sharing a unified database, each site can still offer a unique user experience tailored to its specific purpose.

Note

Parent sites and data centers cannot be changed after the Site Group is created.

Best Practice: Centralized Login Domain

  • Set up a centralized login domain to which all sites in the site group will redirect their login requests.A login page in a Centralized Login Domain handles onLogin request from site A, then redirects back to site with onLogin message. It forwards the login request to Site A in SAP Customer Data Cloud, which then performs the authentication with an external identity provider (SAML, OpenID Connect, or OAuth2). The Returned Access Token is used to send back a Cookie and Login info to the centralized login page. When Site B requests a session from the centralized login domain, it receives an onLogin event with a persisted session.
  • The SAP Customer Data Cloud site hosting the Central Login Page should have the least restrictive policies and is typically the parent site of the Site Group.
  • On a site group, create a login redirect page and include SAP Customer Data Cloud login functionality (via Web SDK & Screen-sets).Child Sites A and B share a Parent Site, which hosts the Central Login Page that both sites redirect to.

For more information, refer to the following documentation in the SAP Help Portal:

Site Groups and single Sign-On and Certificate Provisioning.

Parent and Child Scopes

Child sites inherit Site Policies but can define their own login/registration screen-sets, Email verification, CAPTCHA, and Automated emails. They also inherit Data Schema and Required fields, and can add their own required fields. They can add to the Permissions, Screen-Sets, and Email Templates they inherit, but not to the Identity Access and Web SDK they inherit. Reports exist only at the Child level.

Data Schema

Sites within the same Site Group must have an identical data schema, as they share the same database. Child sites can maintain unique required fields in addition to those inherited from the parent.

Identity Access

Identity Access is accessible from all sites in the site group, providing an overview of the site group's user base, demographics, and preferences.

Site Policies

Most site policies are set on the parent site and apply to the entire site group. Child sites can view the current site policy settings but can only edit a few settings, including:

  • Default login and registration screen-sets
  • Email verification
  • CAPTCHA requirement for new registrations
  • Sending of automated emails (new user welcome, password reset confirmation, account deletion confirmation)

Some policies can only be activated or disabled on the master/parent site but can be fine-tuned on each member/child site.

Permissions

Permissions can be unique per site or shared among all sites.

Screen-Sets

Child sites share the parent's screen-sets by default. However, a child site can use unique screen-sets by duplicating an existing screen-set from the parent or adding a new collection to the site. We recommend changing the name of a child site’s duplicated screen-sets to avoid automatically overriding parent screen-sets with the same name.

Email Templates

Group sites share the same Email Templates by default. A child site can use its own set of templates by checking the "Override parent settings" checkbox on the Email Templates page in the console.

WebSDK Configuration

Child sites inherit the web SDK configuration of the parent site. If you define values for the same parameters in the configuration object of both the parent and child sites, the child's configuration will override the parent's. However, you can use custom code to append the child's settings to those of the parent.

Reports

The Reports tabs (Identity Query Tool & Customer Insights) in the Console displays data only for the selected site, even though data is shared between sites.

For more information, refer to the Implications of Site Groupsdocumentation in the SAP Help Portal.

Demo: Configuring Site Groups

Summary

In this lesson, you learned that:

  • Site Groups enable managing multiple sites with a unified user database and centralized configuration.
  • The Identity Access tool provides a unified overview of the entire site group’s user base and demographics across all member sites.
  • Child sites inherit policies, screen-sets, and email templates from the parent by default, but they have the flexibility to override or fine-tune specific registration and communication settings.