The project follows a unified access model that ensures all users interact with SAP and enterprise solutions in a consistent and secure way, regardless of device type or location. Access methods are defined by the type of device, the data classification, and the nature of the user’s role. All corporate devices are managed through Intune, which ensures that laptops, PCs, and mobile devices remain compliant and secure before connecting to company systems.
In this document we describe access in terms of two concepts.
These are the devices and entry points that people use to reach our systems, for example a corporate laptop, a virtual desktop or a mobile device.
These are the applications and platforms where users perform their work, for example Work Zone Standard, S/4HANA Fiori, SuccessFactors, Ariba, Concur or SAP Analytics Cloud.
Layer | What it represents | Examples |
|---|---|---|
| Access Channels | How users physically reach SAP systems | Corporate Laptop, VDI, Mobile Device, TPA |
| Digital Touchpoints | Where users actually perform their work once inside | Work Zone Standard, Fiori Launchpad, SuccessFactors, Ariba, Concur, SAC |
Legend
Managed Mobile Device: Corporate-managed mobile phone via Intune
Industrial Mobile Device: Rugged handheld or industrial tablet
Unmanaged Mobile Device: Personal device
TPA: Third-Party Access virtual desktop for contractors
Business-Facing Touchpoints
| Corporate Laptop | Virtual Desktop (CUI) | Managed Mobile Device | Industrial Mobile Device | Kiosk | Unmanaged Mobile Device | Third-Party Access (TPA) | |
|---|---|---|---|---|---|---|---|
| Work Zone Standard | Yes | Yes | Yes (2*) | No | Yes | No | Yes (5*) |
| SAP Mobile Start (Mobile Entry Point) | No | No | Yes | No | No | No | No |
| SaaS Applications (Browser / Mobile App) | Yes | Yes | Yes | No | No | Yes | Yes (5*) |
| Industrial Applications | Yes (1*) | Yes (1*) | No | Yes | No | No | Yes (5*) |
| Custom Mobile Solutions (Native or Hybrid) | Yes (1*) | Yes (1*) | Yes | No | No | Yes (4*) | Yes (5*) |
| External Portals | Yes | Yes | Yes (3*) | No | Yes | Yes | Yes (5*) |
IT-Facing Touchpoints
| Corporate Laptop | Virtual Desktop (CUI) | Managed Mobile Device | Industrial Mobile Device | Kiosk | Unmanaged Mobile Device | Third-Party Access (TPA) | |
|---|---|---|---|---|---|---|---|
| SAP GUI for Windows (IT Specialist Access) | Yes | Yes | No | No | No | No | Yes (4*) |
Footnotes
1* Desktop access is provided for configuration, testing, troubleshooting, and supervisory purposes, even though these applications are primarily designed for mobile or industrial devices.
2* Work Zone Standard on mobile is accessed using SAP Mobile Start. Users can still open Work Zone in a mobile browser, but the experience is less optimised. We will not block this, although our recommendation and supported option is SAP Mobile Start.
3* External portals on managed mobile devices follow Intune browser rules.
4* Access on personal devices depends on data classification and business approval.
5* TPA provides a controlled virtual desktop where only approved applications are exposed.
The following sections describe each Access Channel in more detail.
Access channels represent the devices and entry points through which users reach SAP and other enterprise systems. Each channel is defined by its level of control, security, and the type of data it can access. Together they ensure that every user, regardless of role or location, connects through a secure and consistent path that matches their work environment.
Corporate laptops are the standard way most employees access SAP systems. All corporate PCs and laptops are managed through Intune, Syensqo’s device management platform. This ensures that devices remain compliant and secure before connecting to company systems. The design principle is browser first, so business applications are accessed through a web browser rather than installed locally. CUI systems cannot be accessed from standard laptops, and security policies and technical controls are in place to block this.
Virtual desktops are used only when accessing systems that hold CUI-classified data. They provide a secure and segregated environment so that sensitive information does not leave the controlled zone. This setup is required only for users at CUI sites or in roles that work with CUI data. Users still work in a browser inside the virtual desktop, so applications look and behave in a familiar way.
Corporate mobile phones and tablets are managed centrally through Intune, Syensqo’s device management platform. This allows secure configuration, app deployment, and compliance control before a device connects to company systems. Applications are either pre-installed or made available through the company app catalogue. If more than half of a target population needs a specific app, such as SAP Mobile Start or SuccessFactors, the app is pushed automatically. Apps used by smaller populations, such as Concur, are available on demand. Managed mobile devices support single sign on, so users can move between approved apps without repeated logins.
Industrial mobile devices, such as rugged tablets or handheld scanners, are pre-configured for operational use, and only approved business applications are deployed on these devices. User authentication must stay simple and secure. The project will evaluate options such as badge-based login or shared-device patterns, with the goal of keeping user effort low while still enforcing access control.
Today, Syensqo uses more than sixty different industrial device models across plants and warehouses. This creates significant complexity for application design, testing, support, and long-term maintenance because every solution must be validated across many hardware types and operating conditions. As part of the S/4HANA Private Cloud program, the intent is to standardise the fleet to a small set of supported devices, ideally no more than three. Zebra devices are the leading candidates due to their strong industry adoption and the availability of both intrinsically safe and non-intrinsically safe models for different site environments.
Kiosks in Syensqo are fixed, shared terminals used across production, maintenance, laboratory, and operational areas. They are not personal computing devices and do not follow standard end-user sign-in patterns. Each kiosk type supports a specific operational purpose, ranging from displaying production indicators to enabling maintenance scheduling or supporting local shop-floor workflows.
Only a small subset of kiosks interacts with SAP, specifically the GWOS kiosks (see table below). These kiosks currently run the custom transaction ZWPM09A using technical service accounts mapped to the kiosk’s Windows login. As part of the S/4HANA program, we will review ZWPM09A together with the A2D team to determine whether this process continues in the new system. We will also assess whether the current generic-account approach should be replaced with user-based access or an alternative pattern that aligns with the S/4HANA security model.
All other kiosk types will be treated as operational equipment managed by the local IT teams rather than within the scope of SAP UX.*
| Kiosk Type | Expanded Meaning | SAP Access | Used For |
|---|---|---|---|
| Selfy ATM | Selfy “At-The-Machine” Terminal | No | Self-service terminal used next to equipment for simple operator interactions (non-SAP). |
| MES Kiosks | Manufacturing Execution System Kiosks | No | Displaying production indicators, SPC charts, KPIs, PI System dashboards and equipment data in control rooms. |
| GWOS – Input | Global Work Order System – Input Terminal | Yes | Entering or updating Plant Maintenance work orders using SAP technical accounts and barcode scanners (ZWPM09A). |
| GWOS – Display | Global Work Order System – Display Terminal | Yes | Display-only view of work order schedules in PM, refreshed automatically using SAP technical accounts. |
| Generic Kiosks | General-purpose kiosks | No | CCTV, training, surveys, and other non-SAP local applications. |
| Pseudo Kiosks | Local kiosk PCs (SelfyPC, KioskPC, LABPC) | No | Site-specific or ad-hoc kiosks used mainly within labs no SAP access not required. |
Footnote
* Kiosk inventory information is still being consolidated. Current data from IT is fragmented across different teams and systems, and not maintained in a central repository. As part of the S/4HANA program, we are working with IT to confirm which kiosks exist, how they are used, and which ones have SAP access.
Personal mobile devices can be used for selected cloud applications, for example SuccessFactors or Concur, where this is allowed by security policy. Access to core S/4HANA systems and other higher-risk applications continues to require a corporate device or virtual desktop.
Third-party personnel, such as contractors or consultants, will access SAP through the Syensqo Third-Party Access (TPA) workspace. TPA is a secure virtual desktop environment that runs in the browser and provides only the applications that external users need for their work. It keeps all activity isolated from the Syensqo corporate network while still giving a simple and familiar experience.
Access through TPA focuses on what is required for the person’s role. Only the approved SAP applications and business tools are available, and no wider access to the Syensqo network is exposed. This allows external users to perform their tasks safely without compromising internal systems.
Digital touchpoints represent the applications and platforms where users actually perform their work once they have accessed the environment through an approved Access Channel. The objective is to provide a consistent experience across SAP and related enterprise solutions, regardless of device or entry point.
SAP Build Work Zone Standard is the central entry point for all user access. It connects directly to our S/4HANA systems to expose the role-based Fiori apps assigned to each user, and it also links to other enterprise and SaaS solutions such as SuccessFactors, Ariba, and Concur where the role requires them. This gives users one consistent environment to access everything they need for their work without having to remember system names or maintain separate logins.
Work Zone combines content from multiple systems into a single, role-based experience. For example, a procurement specialist can see both S/4HANA Fiori apps and supplier links, while an HR user can access Fiori workflows together with SuccessFactors content. This unified model is one of the core design decisions in our project, providing a consistent user experience and reducing fragmentation while keeping access governed.
In Work Zone, users access applications and content through tiles or links. Tiles represent apps or actions and launch the underlying Fiori app, classic UI, or SaaS system. Each tile displays the app name, icon, and, where relevant, live data or status indicators.
The project uses Insight Tiles (KPI, Chart, Trend, and Comparison) where it makes sense to show key figures or status information directly on the tile. This gives users quick visibility of important metrics before opening the app.
Links are used where a full tile is not needed. They save space and are ideal for opening SaaS homepages, reports, or documentation that support the user’s role. This keeps pages clean and focused.
To maintain clarity as the number of tiles grows, the project follows the new Work Zone layout based on Spaces, Pages, and Sections. This structure keeps navigation consistent and reduces clutter:
Spaces group work by function or Line of Business, such as Finance, Procurement, or HR (maps to Signavio L3).
Pages organise tiles by activity or task type, such as Operational tasks or Analytics (maps to Signavio L4).
Sections further group tiles to make large collections more manageable and reduce visual clutter.
Tiles are the smallest display element and map to Signavio executables (L5).
See images below for examples of the structure and tile types used in Work Zone.
Spaces, Pages and Sections schematic
A schematic display of how Spaces, Pages, and Sections are structured in Work Zone.
Tile Examples image
Examples of different tile types including KPI, Comparison, Monitoring, and Link tiles.
The project operates three SAP Build Work Zone Standard tenants aligned with each regional S/4HANA system. This approach ensures faster access, maintains data segregation by geography, and supports compliance with local performance and regulatory requirements.
Some roles require access to applications in more than one regional instance, such as ROW, CUI, or China. From a user perspective, access across these environments is seamless. Users sign in once and can reach the Work Zone for their region without needing to manage multiple logins or credentials. Aside from the URL, there is no disruption to how users access or work with their applications.
Each Work Zone follows the same structural design so that navigation, pages, and tiles behave consistently across regions. The project is also exploring the use of regional theming to help visually distinguish each tenant, although this is still under review.
Within Work Zone, each tile indicates which backend it connects to, allowing users to identify the system before launching the app. This provides one unified entry point while keeping each region’s data and connectivity governed independently.
See KDD036 - User Access to Enterprise Systems for the technical rationale behind the multi-tenant design.
See images below for examples of how roles access multiple S/4HANA systems through Work Zone.
Individual tiles – used where users need to open separate apps per backend without displaying data. Each tile represents one system and is clearly labelled (for example, Manage Purchase Orders – ROW, CUI, or China).
UI cards – used where data or status values are meaningful at a glance, such as monitoring purchase orders or supplier confirmations across multiple systems. Cards summarise key values in one component, allowing quick comparison without opening separate apps. (Example: “Open PO counts by backend”)
Workflow approvals and tasks are accessed through the Task Centre, which is embedded directly in SAP Build Work Zone Standard. This gives users a single consolidated view of approvals from S/4HANA, SuccessFactors, Ariba, Concur, and any other connected systems. Users can review, approve, or forward tasks without leaving Work Zone, creating a consistent and efficient experience.
The technology team will assess each SAP and non-SAP system to determine whether Task Centre integration is feasible. The SaaS Applications table (See Below) reflects this assessment with three outcomes:
Notifications can be surfaced in SAP Build Work Zone Standard to give users a single place to view important updates from S/4HANA and other connected systems. This includes alerts, status changes, reminders, and Task Centre items, since workflow tasks can also generate notifications. Users can open the related application or record directly from Work Zone, helping them stay informed without switching between systems.
The technology team will assess each SAP and non-SAP system to confirm whether notification integration is possible. The SaaS Applications table (See Below) reflects this with three outcomes:
Figure: Example of notifications displayed in SAP Build Work Zone Standard
Deep linking allows users to open an application or a specific record through a direct URL. Inside S/4HANA and the Fiori ecosystem this works consistently because Fiori supports true deep links and Work Zone acts as the central entry point for navigation.
Outside S/4HANA the experience varies. Each SAP SaaS and non-SAP SaaS product uses its own navigation model, so record-level deep linking is not always available. Some systems support it, others offer only app-level links, and some do not support deep linking at all.
When the business requests a deep link to an external system, the technology team will review the requirement. If the request is valid and within scope, we will assess the capabilities of the target system and confirm what is technically possible. These situations are marked as “Conditional” in the SaaS Applications table below.
Legend for Classification
Legend for Yes / No / Conditional
| Classification | System / SaaS | Description | Task Centre | Notification | Deep Links |
| Core | S/4HANA | Core enterprise system supporting finance, supply chain, manufacturing, and operational processes. | Yes | Yes | Yes |
| Core | SAP GTS | SAP software that helps companies manage and automate international trade processes, focusing on compliance, customs, and logistics | Yes | Yes | Yes |
| Core | SAP Ariba | Comprehensive, cloud-based software solution for managing all stages of the procurement and supply chain process, from sourcing to payment | Yes | Yes | Conditional |
| Core | SAP Concur | Cloud travel and expense system used to submit claims, process travel, and manage reimbursements. | Yes | Yes | Conditional |
| Core | SAP SuccessFactors | Cloud HR suite managing core employee data, talent processes, and workforce performance. | Yes | Yes | Conditional |
| Core | Salesforce | Cloud CRM platform supporting sales, service, and customer engagement processes. | Conditional | Conditional | Conditional |
| Core | Icertis | Cloud contract lifecycle management solution used to create, negotiate, and store commercial agreements. | Conditional | Conditional | Conditional |
| Core | SAP Analytic Cloud (SAC) | Analytics and planning platform for dashboards, forecasts, and business reporting. | No | Conditional | Yes |
| Core | Blackline | Finance cloud solution automating account reconciliations and financial close activities. | Conditional | Conditional | Conditional |
| Supporting Systems | SAP Advanced Financial Closing | Cloud workflow tool coordinating and monitoring period-end financial closing tasks. | Yes | Yes | Yes |
| Supporting Systems | SAP Document Reporting Compliance | Cloud service enabling real-time electronic tax reporting and country-specific compliance. | Yes | Yes | Yes |
| Supporting Systems | SAP Group Reporting Data Collection | Cloud application used to collect, validate, and prepare financial data for group consolidation. | Yes | Yes | Yes |
| Supporting Systems | SAP Profitability & Performance Mgmt. | Financial modelling and profitability analysis platform supporting scenario-based insights. | Conditional | Conditional | Conditional |
| Supporting Systems | SAP Sustainability Footprint Mgmt. | Cloud application calculating product-level environmental footprints. | Conditional | Conditional | Conditional |
| Supporting Systems | SAP Sustainability Control Tower | Sustainability reporting platform consolidating KPIs across the enterprise. | Conditional | Conditional | Conditional |
| Supporting Systems | SAP Green Ledger | Carbon accounting ledger aligning environmental metrics with financial structures. | Conditional | Conditional | Conditional |
| Supporting Systems | SAP BN Global Track & Trace | Shipment visibility platform providing real-time tracking across logistics partners. | Conditional | Conditional | Conditional |
| Supporting Systems | SAP BN Freight Collaboration | Cloud service connecting shippers and carriers to manage freight orders and status updates. | Conditional | Conditional | Conditional |
| Supporting Systems | SAP Asset Performance Mgmt. | Cloud solution for monitoring equipment health and improving maintenance outcomes. | Conditional | Conditional | Conditional |
| Supporting Systems | SAP Risk and Assurance Mgmt. | Cloud platform used to document risks, controls, and assurance activities. | Yes | Yes | Conditional |
| Supporting Systems | PCN Opesus (SAP add-on) | Product compliance notification tool used for EU and UK regulatory submissions. | Conditional | Conditional | N/A |
| Supporting Systems | Keelvar | AI-enabled sourcing optimisation solution supporting complex procurement categories. | Conditional | Conditional | Conditional |
| Supporting Systems | Kinaxis Maestro | Supply chain planning platform supporting scenario planning and forecasting. | Conditional | Conditional | Conditional |
| Supporting Systems | (3E Optimize)/VSDS Loader | Cloud service supporting chemical safety data and regulatory information handling. | No | No | Conditional |
| Supporting Systems | AVEVA PI-AF (MES) | Manufacturing data historian capturing process data for analysis and reporting. | No | No | Conditional |
| Supporting Systems | CASS | Freight audit and payment service validating logistics invoices and charges. | No | No | Conditional |
| Supporting Systems | Esker | AP automation platform supporting invoice capture, routing, and approval workflows. | Conditional | Conditional | Conditional |
| Supporting Systems | EDICOMM | e-Invoicing and EDI compliance platform used for country-specific reporting. | Conditional | Conditional | Conditional |
| Supporting Systems | Vertex O Series | Cloud tax engine calculating indirect taxes for sales and invoicing processes. | Conditional | Conditional | Conditional |
| Supporting Systems | Worldline (SWIFT) | Banking connectivity service enabling SWIFT messaging for treasury operations. | No | No | Conditional |
| Supporting Systems | OpenText | Document management platform integrating structured content with SAP business objects. | Conditional | Conditional | Conditional |
| External Partner Platforms | Bloomberg | Financial market data service providing pricing, rates, and analytics for treasury processes. | No | No | Conditional |
| External Partner Platforms | UPS | International courier and logistics provider supporting parcel shipping and delivery tracking. | No | No | Conditional |
| External Partner Platforms | FEDEX | Global parcel and freight carrier used to book shipments, generate labels, and track deliveries. | No | No | Conditional |
| External Partner Platforms | DHL | Global express and freight logistics provider used for outbound shipments and tracking. | No | No | Conditional |
| External Partner Platforms | Project44 | Logistics visibility platform providing real-time shipment tracking across carriers. | Conditional | Conditional | Conditional |
| External Partner Platforms | Sunland Infor | Asian logistics partner providing warehousing, distribution, and transport services. | No | No | Conditional |
| External Partner Platforms | Kenco | North American logistics provider offering warehousing, distribution, and transportation services. | No | No | Conditional |
| External Partner Platforms | TMS4S / E2Open (BluJay) | Transportation management system supporting carrier bookings, loads, and tracking. | Conditional | Conditional | Conditional |
| External Partner Platforms | Mitsui Soko | Japanese logistics and warehousing provider supporting storage and transport operations. | No | No | Conditional |
| External Partner Platforms | PML CN | China-based logistics partner supporting regional warehousing and transportation activities. | No | No | Conditional |
| External Partner Platforms | Transwide TMS | Transportation planning and tendering platform used for carrier selection and load execution. | Conditional | Conditional | Conditional |
| External Partner Platforms | Katoen Natie 3PL (Belgium) | International 3PL providing storage, handling, and distribution for Syensqo sites in Belgium. | No | No | Conditional |
| External Partner Platforms | Katoen Natie (Global) | Global 3PL provider offering warehousing, handling, and logistics services across multiple regions. | No | No | Conditional |
| External Partner Platforms | Arcese 3PL Italy | Third-party logistics provider supporting warehousing and transport operations in Italy. | No | No | Conditional |
Joule is SAP’s built-in generative AI assistant that helps users work faster and with fewer manual steps. It can answer questions, summarise information, create insights, and guide users through processes using natural language. In our S/4HANA landscape Joule will support everyday business activities such as reviewing transactions, analysing documents, identifying issues, and recommending actions based on the data in the system.
For business users the main benefit is simplicity. Instead of navigating multiple screens or searching for the right application, users can ask Joule a question or describe what they want to do. Joule can open the correct app, retrieve relevant information, or complete routine tasks on the user’s behalf. This creates a more intuitive and productive experience, especially for infrequent users or users who work across multiple systems.
We will make Joule available through SAP Build Work Zone Standard as one of the core access points for AI support. Users will be able to launch Joule directly from Work Zone to ask questions, request guidance, or trigger actions in S/4HANA and connected systems. As SAP expands Joule’s capabilities, the assistant will become a central touchpoint for insights, help, troubleshooting, and process support.
During the project the technology and functional teams will work with SAP to test Joule in realistic business scenarios. This includes validating how well Joule understands our processes, the accuracy of its responses, and how it can speed up tasks for each Line of Business. The objective is to identify high-value use cases and provide guidance to users so the organisation gets the most benefit from the AI capabilities SAP delivers.
SAP Build Work Zone Standard and the related SAP Fiori applications require a modern, fully supported web browser. Using the latest version ensures the best performance, security, and user experience. Older or unsupported browsers can cause missing features, display issues, or login problems.
See SAP documentation: Browser and Platform Support
Figure: Supported browsers for accessing SAP Build Work Zone and Fiori apps
Understanding how different users interact with SAP systems helps define which access channel is most suitable for their role. These categories guide which front-end technology is recommended, including SAP Fiori, SAP Build Work Zone Standard, SAP Mobile Start, desktop browsers, or occasional use of SAP GUI for IT specialist functions.
This classification supports the UX design by aligning each user type with the most appropriate experience.
| Usage Type | Description | Typical Characteristics | Recommended Technology |
|---|---|---|---|
| Expert Usage | Users who work in the system frequently and develop deep familiarity with their applications. | Several hours of exposure each week. Desktop focused. Creates and edits business data. Requires structured training. Priorities include productivity and clarity. | SAP Fiori apps via Work Zone (desktop). Analytical apps. SAP GUI for specialist functions. |
| Regular Usage | Users who interact with SAP as part of their daily routine but not for long periods. | Daily usage but a small set of transactions. One to five hours per week. Reviews information or approves items. Requires basic training. Priorities include simplicity and efficiency. | SAP Fiori via Work Zone. My Inbox for workflow. Mobile Start for quick tasks. |
| Occasional Usage | Users who access SAP infrequently and do not build ongoing familiarity with applications. | Once a week or less. Minimal time in the system. Often limited to viewing or approving. Suitable for mobile or tablet. Minimal system training. Priorities include simplicity and ease of use. | Work Zone tiles and guided navigation. Mobile Start. Lightweight Fiori apps. Deep links from emails or notifications. |
Industrial applications are deployed on rugged or shared devices such as Zebra scanners to support plant, maintenance, and logistics operations. These solutions provide task-focused mobile workflows, scanning capabilities, offline support where needed, and seamless integration with S/4HANA. Below is the initial list of confirmed industrial applications for Syensqo.
| Application | Purpose | Key Capabilities |
|---|---|---|
| BlueWorx (Neptune-based) | Flexible and configurable mobile EAM solution. | Work order processing, inspections, notifications, asset data capture. Strong offline support, efficient sync, consistent mobile and desktop experience. |
| Logistics Mobile Solution (LMS) | Mobile scanning and execution for warehousing and logistics. | Handheld scanner solution with online and offline capability. Supports unified inbound and logistics flows across IM-NonHU, IM-HU, and EWM without multiple separate apps. |
Mobile access supports users who need quick, on-the-go entry to tasks, approvals, and business information. SAP Mobile Start provides the primary entry point to S/4HANA and Work Zone content, while additional mobile applications from solutions such as Concur, SuccessFactors, and other SaaS products are made available through the company app catalogue. The intent is to provide secure, role-based access on mobile devices and maintain a consistent experience across desktop, tablet, and phone.
Email and SMS alerts are not recommended as primary communication channels for the S/4HANA Private Cloud program. With SAP Build Work Zone Standard providing Task Centre and in-platform notifications, we already have a consistent and centralised way to reach users for tasks, approvals, and system updates. Relying on external email or SMS channels increases noise, creates duplicated messages, and reduces the overall user experience.
There will be valid exceptions. Certain external processes, such as DocuSign, depend on email-based notifications as part of their standard workflow. There may also be cases where messages must be sent to users outside the organisation. These situations will be reviewed on a case-by-case basis to confirm the business need and determine the correct technical approach.
The objective is to minimise unnecessary email and SMS alerts and encourage the use of consolidated, in-platform notifications through Work Zone Standard for all internal users.
A separate Microsoft programme is currently running in Syensqo to define the future strategy for collaboration and productivity tools. This work is expected to conclude in the second quarter of next year. The outcomes of that programme will determine which Microsoft tools are recommended for enterprise use, including Microsoft Teams. Once the direction is confirmed, the SAP project will assess how these tools can work alongside Work Zone Standard, S/4HANA, and other touchpoints. Any integration approach will be tested to confirm the value for business users and ensure it aligns with our security, access, and data governance model.
Below is an overview of how Microsoft Teams can potentially integrate with SAP systems and what may be considered once the Microsoft programme is final.
| Capability | How it Can Work with SAP | Notes |
|---|---|---|
| Notifications | Teams can receive alerts or workflow notifications forwarded from SAP systems. | Must avoid duplication with Work Zone and Task Centre. |
| Approvals | Selected SAP approvals can be actioned through Teams connectors. | Only if value is proven and governance is in place. |
| Tabs / Quick Access | Teams channels can host tabs that open Work Zone, SAC stories, or SAP applications. | Convenience only. Work Zone remains the primary entry point. |
| SAC Embedding | SAC dashboards can be displayed inside Teams channels. | Useful for team collaboration around KPIs and analytics. |
| Chat-based Interaction | Bots or assistants can connect Teams to SAP backend services. | Future potential depending on SAP Joule external integration. |
| Document / Process Collaboration | Teams is used to collaborate around SAP-related work (meetings, files, discussions). | Complements SAP but does not replace system-of-record functions. |
External portals support interactions with customers, suppliers and other business partners. Examples include supplier portals, B2B portals and customer access to Safety Data Sheets. These portals are separate from internal systems but follow similar principles for branding and ease of use.
WalkMe is a digital adoption platform that guides users through complex applications by providing on-screen, step-by-step assistance. It helps users complete tasks correctly by overlaying prompts, walkthroughs, and guidance directly on top of the system they are using, without modifying the underlying application. Our program supports WalkMe and will utilise it as part of the overall user enablement approach. However, some applications, especially industrial mobile solutions, can be sensitive to performance overhead. In these cases WalkMe may introduce latency or slow the user interface. Where this occurs, we will address the situation pragmatically. One option is to provide two versions of the application, one with WalkMe enabled and another with WalkMe removed, ensuring that operational processes remain fast and practical while still offering guided support where appropriate.