Please log in to continue
WalkMe stores your data in the region chosen during account setup.
We have data centers in the US and EU that follow local privacy and compliance laws. If you're not sure which region to select, check with your admin.
This document covers access requirements for WalkMe users and end-users, all the domains listed below should be accessible via the HTTPS protocol on port 443 (this configuration is typically handled by the IT team at your organization).
The WalkMe Player is how End-users view your published WalkMe Solutions.
The WalkMe Editor Software and WalkMe Insights Web Portal are modules where you can manage your WalkMe Solutions and view data gathered on site and WalkMe usage.
In order to view WalkMe content as an end-user, the following domains need to be accessible:
If these domains are blocked, core capabilities of the WalkMe Player cannot function.
| Domain | Purpose of Domain | If Access is Blocked |
|---|---|---|
| cdn.walkme.com | Download static JS files and CSS files necessary for the WalkMe Experience | Unable to view WalkMe Published content |
| playerserver.walkme.com | Hosts content related to WalkMe Applications | Several WalkMe Applications will not work (e.g. Search, Onboarding Tasks, Goals, Survey) |
| ec.walkme.com | Send end-user meta-data to WalkMe Insights Servers | WalkMe Insights Data will not be collected |
| papi.walkme.com | Hosts content related to WalkMe Applications | Several WalkMe Applications will not work (e.g. ChatBot, IDP Integration) |
| s3.walkmeusercontent.com | Images in WalkMe Solutions hosted by WalkMe’s AWS | Images in WalkMe Solutions that are hosted by WalkMe’s AWS will not appear |
| workstation.walkme.com | Used by the Workstation product | Core functionality of the WalkMe Workstation will not work |
If these domains are blocked, some capabilities of the WalkMe Player cannot function.
| Domain | Purpose of Domain | If Access is Blocked |
|---|---|---|
| ec-playback.walkme.com | Send end-user meta-data to WalkMe Insights Servers | WalkMe Session Playback will not work |
| clients2.google.com/service/update2/crx | Update Chrome extensions | WalkMe Chrome extensions (Player and Editor) will not be able to update |
| safari-extensions.apple.com/details/ | Update Safari extensions | WalkMe Safari extension (Player and Editor) will not be able to update |
If you have concerns about your WalkMe Player End-users accessing these domains above, please reach out to your WalkMe representative.
Since WalkMe Editor users also view and preview their content using the WalkMe Player, Editor users require access to domains on both the “WalkMe Player End User” list above, as well as
the below items.
For users of the WalkMe Editor and Insights Portal, it is recommended the following domains are accessible for the best experience:
| Domain | Purpose of Domain | If Access is Blocked |
|---|---|---|
| *.walkme.com | Load the WalkMe product | WalkMe will not function |
| s3.walkmeusercontent.com | WalkMe-hosted images | Some images, including images uploaded by the user via the Editor, will not be displayed |
In cases where allowing a wildcard domain is not possible, below is a more detailed listing of required domains.
If these domains are blocked, core capabilities of the WalkMe Editor or Insights Portal cannot function.
| Domain | Purpose of Domain | If Access is Blocked |
|---|---|---|
| cdn.walkme.com | Download static JS files and CSS files necessary for WalkMe Editor | WalkMe Editor and Insights Portal will not function |
| api.walkme.com | Access various API endpoints of WalkMe products | WalkMe Editor and Insights Portal will not function |
| editor.walkme.com | Save/edit/manage solutions created in the Editor | WalkMe Editor will not function |
| editorsite.walkme.com | Load the WalkMe Editor | WalkMe Editor will not function, some features in Insights Portal will not function |
| portal.walkme.com | Load resources related to WalkMe Editor and Insights Portal | WalkMe Editor and Insights Portal will not function |
| auth.walkme.com | Login to WalkMe Editor and/or WalkMe Insights | User cannot log into WalkMe Editor and/or WalkMe Insights |
| admin.walkme.com | WalkMe admin center | User cannot manage sub-users in their account and other account-related configuration |
| console.walkme.com | Provide access to WalkMe apps | User cannot use WalkMe apps (such as Menu Organizer, Communication Center) |
| web.apps.walkme.com | Host WalkMe Console apps | User cannot use WalkMe apps |
| api.apps.walkme.com | Host API endpoints related to WalkMe apps | User cannot use WalkMe apps |
| s3.walkmeusercontent.com | WalkMe-hosted images | Images in WalkMe Solutions that are hosted by WalkMe’s AWS will not appear, additional images cannot be hosted by WalkMe’s AWS |
| insights2.walkme.com | View WalkMe Insights Dashboards | WalkMe Insights Portal will not be accessible |
| insights.walkme.com | Load content related to the Insights Portal | Some functionality in WalkMe Insights Portal will not work |
| insights-cdn.walkme.com | Load static content related to the Insights Portal | Some functionality in WalkMe Insights Portal will not work |
| insights-reports.walkme.com | Generate reports in Insights Portal | Reports in Insights Portal will not work |
Please note that the WalkMe Editor requires the allowance of third-party cookies on your browser. Otherwise, it will continuously generate a “Please wait for page to load” or a “reload the page if a long while has passed.” message that does not go away even after refreshing the page.
If these domains are blocked, some capabilities of the WalkMe Editor or Insights Portal cannot function.
| Domain | Purpose of Domain | If Access is Blocked |
|---|---|---|
| share.walkme.com | Used by WalkMe Share | User cannot share WalkMe content |
| accounts.walkme.com | Login via customer's own IDP | Customers with IDP integration configured will not be able to login |
| communication-center.walkme.com | Host the Communication Center | Communication Center app will not work |
| menuorganizer.walkme.com | Host the Menu Organizer app | Menu Organizer app will not work |
| analytics.walkme.com | Manage Multi-Language content | User will not be able to create Multi-Language content |
| logs.walkme.com | Collect metadata for diagnostic purposes | WalkMe will have difficulties assisting with technical issues |
| walkme.wixanswers.com | Required for WalkMe Chat Support | WalkMe Chat Support will not function |
| frog.wix.com | WalkMe Chat Support metadata collection | WalkMe Chat Support will not receive metadata |
| fonts.googleapis.com | CSS for Insights | WalkMe Insights may have visual issues |
| fonts.gstatic.com | CSS for Insights | WalkMe Insights may have visual issues |
| web-client.apps.walkme.com | Used by WalkMe Editor apps | Some WalkMe Editor apps (e.g. Solution Templates) will not work |
| data-apps.walkme.com | Used by WalkMe Insights apps | Some WalkMe Insights apps (e.g. Activity Dashboard) will not work - Takes effect January 2023 |
| *.zoom.us | Zoom Support Chat | Support Chat on the WalkMe Help Center will not work |
If these domains are blocked, some capabilities of the WalkMe Editor cannot function.
| Domain | Purpose of Domain | If Access is Blocked |
|---|---|---|
| teachme.walkme.com | Use WalkMe TeachMe Product | Cannot create WalkMe TeachMe Solutions |
| playback-assets.walkme.com | View Session Playback Product | Cannot view Session Playback feature in WalkMe Insights |
The list of domains used by WalkMe may change from time to time as our product evolves. If keeping up with these changes is important in your organisation, we advise you to subscribe to receive automated email notifications on changes to this list.