SAP Build Work Zone, standard edition, provides built-in capabilities for role-based personalization. The most efficient and scalable approach is to use dynamic groups (based on user attributes from the identity provider) and then target content, such as pages and apps, to those groups. This ensures content is automatically relevant without manual per-user maintenance.

To consume content from an SAP BTP, Cloud Foundry environment (like SAP Fiori apps), you must first register that environment as a content provider in the Content Manager. This establishes a trust connection and allows the system to discover the available HTML5 apps and services from that provider, which can then be assigned to workspaces and groups.

The Page Builder is the core tool for creating pages in a workspace. Its drag-and-drop interface and library of widgets (like the ‘App Launcher’ for Fiori apps, ‘Web Page’ for external content, and ‘News’ widget) allow administrators to compose integrated pages that bring together content from different sources into a unified layout.

The ‘Delegate Content Administration’ feature allows a super administrator to delegate the management of content (like pages and apps) for specific dynamic groups to other users. This empowers department heads to tailor content for their teams while the central IT team retains control over the overall site structure, branding, and provider configurations.

While the SAP Fiori launchpad is excellent for launching SAP Fiori apps, SAP Build Work Zone extends this into a broader digital workplace. Its core advantage is aggregating and contextualizing content from diverse sources—SAP Fiori apps, external URLs, news feeds, etc.—into personalized workspaces for different user roles, going beyond just SAP applications.

SAP Build Work Zone allows administrators to define a global theme for the site, including colors, logos, and fonts. This branding is applied to the shell and framework of the work zone. While it won’t redesign internal third-party application pages, it creates a consistent header, navigation, and shell experience, making the overall workspace feel more unified.

External web applications can be added as ‘Web Page’ content. The key practical consideration is authentication. If the app has its own login, users will typically be prompted for credentials when they access it (a ‘break in glass’ experience). For seamless SSO, the external app would need to trust the same identity provider (like SAP IAS/IPS), which requires configuration on both sides, often handled via a destination.

The ‘Space Administrator’ role is the appropriate role for creating and managing the lifecycle of workspaces (spaces). A Content Administrator manages the content (apps, pages) within spaces they are delegated to, but typically does not create the spaces themselves. End Users and Viewers only consume content.

SAP Cloud Identity Services (specifically Identity Authentication Service – IAS and Identity Provisioning Service – IPS) are the cornerstone for managing external identities in the SAP BTP context. IAS acts as an identity provider for business-to-business (B2B) and business-to-consumer (B2C) scenarios, allowing you to onboard, authenticate, and authorize partner users without needing them in your internal directory.

SAP Build Work Zone, standard edition, provides built-in capabilities for role-based personalization. The most efficient and scalable approach is to use dynamic groups (based on user attributes from the identity provider) and then target content, such as pages and apps, to those groups. This ensures content is automatically relevant without manual per-user maintenance.0