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 Learning Arc users and end-users, the term “accessible” used in the document refers specifically to access via the HTTPS protocol on port 443 (this configuration is typically handled by the IT team at your organization).
In order to view WalkMe Learning Arc 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 Learning Arc experience |
Unable to view WalkMe Learning Arc published content |
| playerserver.walkme.com |
Hosts content related to WalkMe Applications |
Some WalkMe content will not work |
| ec.walkme.com |
Sends user metadata to WalkMe Insights servers |
WalkMe Insights data will not be collected |
| papi.walkme.com |
Authenticating end users into the portal |
Authenticating to Learning Arc will not work |
| s3.walkmeusercontent.com |
Holds assets in WalkMe Learning Arc hosted by AWS |
Hosted assets in WalkMe Learning Arc will not appear |
| portal.us.wmlearningarc.com |
Used to access the WalkMe Learning Arc Portal Note: It is also possible to define (and then allow), a custom domain instead, such as: customer1.us.wmlearningarc.com |
Users will be unable to access WalkMe Learning Arc |
If these domains are blocked, some capabilities of the WalkMe Player cannot function.
|
Domain |
Purpose of domain |
If access is blocked |
|---|---|---|
|
Update Chrome extensions |
WalkMe Learning Arc extension will not be able to update |
For WalkMe Learning Arc builders and those using Insights, it is recommended the following domains are accessible for the best experience:
|
Domain |
Purpose of domain |
If access is blocked |
|---|---|---|
| *.walkme.com |
Load WalkMe Learning Arc |
WalkMe Learning Arc will not function |
| s3.walkmeusercontent.com |
WalkMe-hosted images |
Some images, including images uploaded by the builder, will not be displayed |
If these domains are blocked, core WalkMe capabilities cannot function.
|
Domain |
Purpose of domain |
If access is blocked |
|---|---|---|
| cdn.walkme.com |
Download static JS files and CSS files necessary for WalkMe Learning Arc |
WalkMe Learning Arc will not function |
| api.walkme.com |
Access various API endpoints of WalkMe Learning Arc |
WalkMe Learning Arc will not function |
| editor.walkme.com |
Various API endpoints related to generating content |
WalkMe Learning Arc will not function |
| auth.walkme.com |
Login to WalkMe Learning Arc |
Users cannot log into WalkMe Learning Arc |
| 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 |
WalkMe Learning Arc will not function |
| 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 |
| insights-reports.walkme.com |
Generate Insights reports |
Reports in Insights Portal will not work |
| web-client.apps.walkme.com |
Used by some WalkMe apps |
Some WalkMe apps will not work |
| data-apps.walkme.com |
Used by WalkMe Insights apps |
Some WalkMe Insights apps will not work |
If these domains are blocked, some WalkMe capabilities cannot function.
|
Domain |
Purpose of domain |
If access is blocked |
|---|---|---|
| logs.walkme.com |
Collect metadata for diagnostic purposes |
WalkMe will have difficulties assisting with technical issues |
|
CSS for Insights |
WalkMe Insights may have visual issues |
|
|
CSS for Insights |
WalkMe Insights may have visual issues |