The correct and standard method is to map the SAP BTP user group (which contains the department users) to a role collection in the SAP Build Work Zone admin cockpit. This role collection is then assigned to the application for visibility control. This leverages the centralized identity management and is scalable and secure, unlike manual user assignment. Creating a new Space is a more heavy-handed structural change for a simple visibility need.

Page Variables are designed specifically for dynamic, page-level data binding. Their primary use case is to facilitate communication between widgets on the same page. For example, selecting an item in a list widget can store a value (like a cost center) in a Page Variable, which is then read by a chart widget to filter its data accordingly. Site-level constants (logo, theme) are better set in Theme Designer or site properties, and user context is typically handled by the system or user-specific variables.

A Site is a top-level, fully independent launchpad with its own content, navigation, theme, and user management. Assigning an HR user as the Site Manager delegates administrative control (like adding apps and pages) to the business department, fulfilling the requirement for autonomy. A Group or Page within an existing site would not offer the same level of separation, distinct branding, or independent management capabilities.

For a remote Fiori app (like from S/4HANA), two key prerequisites are needed: system connectivity and user authorization. First, the source system (S/4HANA) must be registered as a content provider in the SAP Build Work Zone admin cockpit to establish trust and connectivity. Second, the end user must have the required business role/authorization in the S/4HANA backend to actually use the app. The launchpad itself only provides the launch tile; it does not bypass backend security.

A Group is the primary navigation element used to create a hierarchical menu structure. You create a Group (e.g., ‘Financial Reports’) and then assign multiple Pages or Links to it. In the runtime site, ‘Financial Reports’ appears as a single menu item that users can click to expand and see the individual items within it. This prevents cluttering the main navigation bar.

This is a common point of confusion. The ‘Site Manager’ role has broad privileges, including design changes. However, these actions are only available in the Site Editor mode. If the user is viewing the live, published site (runtime), the editing controls are not visible. They must explicitly enter the editor via the ‘Edit Site’ action (often found under a user menu or admin entry point) to access tools for changing themes and layouts.

The ‘URL’ app type is precisely designed for this purpose. It allows an administrator to create a launchpad tile that acts as a direct link to any URL-based resource, including external websites and web applications. This is the simplest and most common way to integrate non-SAP web content. Packaging it as a SAPUI5 app is unnecessary overhead for a simple link.

This is a fundamental security concept. A Role is the most granular unit of permission (e.g., ‘Site Manager’, ‘Content Manager’, ‘Viewer’). A Role Collection is a reusable basket that contains one or more of these Roles. Administrators assign Role Collections to users/groups, not individual Roles. This simplifies user management (e.g., a ‘Country Manager’ Role Collection might contain several specific Roles).

The browser’s developer console is the primary tool for front-end troubleshooting. It will show if the widget’s code has errors, if it’s trying to call an incorrect or unauthorized API endpoint, or if there are network issues (CORS, authentication failures). This provides immediate, specific clues. Recreating the page or contacting support should be later steps, taken after gathering evidence from the console.

The correct and standard method is to map the SAP BTP user group (which contains the department users) to a role collection in the SAP Build Work Zone admin cockpit. This role collection is then assigned to the application for visibility control. This leverages the centralized identity management and is scalable and secure, unlike manual user assignment. Creating a new Space is a more heavy-handed structural change for a simple visibility need.0