What Is SAP Build Work Zone?
SAP Build Work Zone is the central entry point for your business users — a launchpad where Fiori apps, dashboards, workflows, and content from multiple systems appear in one place.
If you have built custom Fiori apps before, Work Zone is where those apps become discoverable. Instead of bookmarking five different URLs, users open one launchpad and see everything they are allowed to use.
Before You Start: Prerequisites
- An SAP BTP subaccount with the SAP Build Work Zone, standard edition service entitled.
- An identity provider configured on the subaccount (the default SAP ID service works for a first setup).
- A content provider or at least one Fiori app you want to expose — even a sample app is fine for learning.
Step 1: Create the Service Instance
In your BTP cockpit, go to your subaccount → Services → Service Marketplace, find "SAP Build Work Zone, standard edition", and create an instance with the standard plan.
Then create a service key for the instance. The service key gives you the launchpad URL — that is your Work Zone site address.
Step 2: Assign Yourself an Admin Role
Open your subaccount's Security → Users, find your user, and assign the Work Zone admin role collection (it is named after the service, typically containing "Admin" in the name).
Without this role, the site administration pages stay hidden. If you can see the launchpad but not the "Site Manager", a missing role is the reason.
Can see apps but not the admin pages? It is a role assignment issue, almost every time.
Step 3: Build Your First Page
Open the Work Zone site, go to Site Manager → Pages, and create a page. Pages are the canvases users land on — a home page, a team page, a project page.
Add widgets to the page: app tiles, feed widgets, or HTML content. Arrange them by drag and drop. Keep the first page simple — three to five tiles beats a crowded dashboard nobody scans.
Step 4: Add Apps via Content Channels
Apps enter Work Zone through content channels. Go to Site Manager → Content Manager and connect a provider — for example, an ABAP system via a content federation destination, or an HTML5 app deployed on BTP.
Once connected, assign the apps to roles, then drop them onto your page as tiles. A tile is just a pointer: title, icon, and target app.
Step 5: Publish and Share
Pages start as drafts. When the layout looks right, publish the page and assign it to a role so the right users see it. Open the launchpad in an incognito window to sanity-check what a regular user experiences.
Always verify as a non-admin user. Admin views hide half the problems your users will hit.
That is a working launchpad: service instance, admin role, one page, a few tiles, published. Everything after this is refinement.
Questions? Drop them in the comments.