Scopes for Adapting Content

As an administrator you can adapt the content delivered by SAP within SAP Fiori launchpad for the roles within your company using the SAP Fiori launchpad designer.

SAP delivers predefined content like catalogs and groups for the SAP Fiori launchpad. As an administrator you can use the launchpad designer to copy and adapt the content in the configuration and customizing scopes.

The predefined SAP Fiori launchpad content uses the Web Dynpro configuration as persistence tool. The content is stored in the following scopes:

Table 1:
Scope	Description	Tool
Configuration	System-wide settings The content delivered by SAP is stored in the configuration scope. Administrators can use the configuration scope to copy a catalog. Then they adapt the copied catalog in the customizing scope for a selected client. To access the launchpad designer in the configuration scope, add parameter `scope=CONF` to the URL.	SAP Fiori launchpad designer
Customizing	Client-specific settings Content changes are valid only for the current client. These settings supersede configuration settings, but can be superseded by personalization settings. Administrators can use the customizing scope to copy a catalog and to adapt it for a selected client. If you access the launchpad designer without providing any scope parameter in the URL, the customizing scope is selected by default. The parameter you can add to the URL is `scope=CUST`.	SAP Fiori launchpad designer
Personalization	User-specific settings End users can use the personalization scope to adapt a group that contains predefined content and that has been assigned to their user role by an administrator. They can rearrange the tiles in the SAP Fiori launchpad and save their preferences in the personalization layer. These settings supersede customizing and configuration settings.	SAP Fiori launchpad

The client information for the relevant scope is displayed in the launchpad designer header next to the SettingsFLD icon:

A specific client (for example, 000) for the customizing scope
Client: ALL for the configuration scope

If the content exists in more than one scope and you change it in a more specific scope (for example, personalization), the changes supersede the content stored in a more generic scope (for example, configuration).

For example, if you make changes to a catalog in the content delivered by SAP and stored in the configuration scope after you personalized the content, these changes are not visible in the personalization scope.

If you delete the whole group or catalog in the personalization scope or in the customizing scope, the system displays the original data of the less specific scope. To delete content, drag an entity (for example, a group) to the trash can in the launchpad designer.

If you delete a catalog or group in the customizing scope, the launchpad designer tries to load the object from the layer of the configuration scope. If this is successful, a message will let you know that the object has been reloaded from a lower layer.