If you customize a business role template, you must also check the associated spaces and pages. Ensuring that customizations are applied consistently across these elements maintains a uniform user experience.
It is important to distinguish between business catalogs and space/page templates. While business catalogs within a role grant access to applications, the space/page template determines whether those applications actually display on the launchpad.
SAP provides standard space and page templates for each business role to offer a clean display of essential apps. However, when creating custom business roles, you must also create custom spaces and pages. You can use standard versions as a starting point, but custom roles require their own dedicated spaces and pages to define the launchpad layout for end users.

Navigate to the Launchpad Page Assigned to a Space and Business Role
In the Maintain Business Users app, a standard business role should always have at least one assigned launchpad space. This is typically the SAP standard space designed for that role.
In the Type column, the status managed by customer indicates that you can modify the space and its assigned pages. If the status is managed by SAP, the space and its pages are read-only and cannot be changed.

- In a customized business role, go to the Assigned Launchpad Spaces tab and select the space.
- In the Manage Launchpad Spaces app, identify the assigned page and select it.
- In the Manage Launchpad Pages app, you can view the apps in each section. Select Edit to add or remove apps or to modify their visual layout.
Add, Remove, and Modify the Visual Display of Apps
The Derived from Roles list on the right shows apps available through the business catalogs assigned to the role. This serves as a master list of apps you can add to the launchpad page based on existing permissions.
To add apps not found in this list, select the ... (three dots) icon below the Page Preview. Note that you must also assign the corresponding business catalog to the business role to ensure users have the necessary permissions to run the app.
When adding or editing an app, you can choose from several display formats:
- tile (default)
- wide tile
- link
- flat tile
- flat wide tile

Identify an App to Add to the Launchpad Page
If an app is missing from the Derived from Roles list, use the SAP Fiori Apps Reference Library to find the required business catalog.
Once you have the catalog ID, you can manually add the app to the page and then update the business role permissions. For example, to add the Manage Teams and Responsibilities app to a Project Management role:

- Search for the app in the SAP Fiori Apps Reference Library and select the correct deployment version.
- Go to the Implementation Information tab and open the Configuration section.
- Locate the Business Catalog(s) section and copy the relevant ID.
- Return to the Manage Launchpad Pages app in SAP S/4HANA Cloud.
- Select the ... (three dots) icon and choose Select Catalogs.
- Search for the catalog using the ID you copied and select it.
- Confirm the selection. You can then view the Catalog Description to understand relevant fields for defining restrictions.
Add an App Outside the Scope of Business Catalog Permissions
After selecting a business catalog, the apps appear in the Manually Selected section. Choose a display format and assign the app to a page section.
The app will initially show a red "X". This indicates that while the app is on the page template, it will not be visible to users because the required business catalog has not yet been assigned to their business role.
Note
You can save the page and return to the business role settings by clicking Back twice.

Assign the Business Catalog and Verify the Launchpad Page
In the Maintain Business Roles app, go to Assigned Business Catalogs. Add the catalog for the Manage Teams and Responsibilities app and select Save.
You may be prompted to add dependent catalogs. Once saved, navigate back through Assigned Launchpad Spaces→select the space→select the page. The red "X" should now be gone, as the app is now within the scope of the role's permissions.

Hint