Brief Overview

Enterprise Mode provides additional control over how WalkMe runtime versions are updated. When enabled, it separates content publishing from runtime version updates, allowing builders to decide when a new WalkMe runtime version is adopted instead of updating automatically during every publish.

This mode is intended for organizations that require stricter governance, testing, or security controls around runtime changes.

Use Cases

Use Enterprise Mode when you need to:

• Test new WalkMe functionality in Test before updating Production
• Control when runtime versions change due to security or compliance requirements
• Prevent automatic runtime updates from impacting production behavior

How It Works

When Enterprise Mode is enabled:

• WalkMe runtime JavaScript files are frozen at a specific version
• Publishing content does not automatically update the runtime
• Runtime updates occur only when explicitly selected by the builder

Publishing content continues to update Settings and Data files, which contain account configuration and WalkMe content such as Smart Walk-Thrus and ShoutOuts, while runtime files remain unchanged until a runtime update is performed.

This update freezes the runtime files marked in blue in the flowchart below, and a timestamp is added for future reference.

Publish Behavior

Enterprise Mode introduces two publish actions:

• Publish: Publishes content using the currently frozen runtime version
• Updated Publish: Publishes content and updates the WalkMe runtime to the latest available version

Multiple publishes can use the same runtime version until an updated publish is performed.

The table below illustrates example publish behavior when Enterprise Mode is enabled.

Preview Behavior

Enterprise Mode allows builders to preview content using:

• The current runtime version deployed to the environment
• The latest available runtime version for evaluation

This enables comparison before deciding whether a runtime update is required.

Updating WalkMe's Runtime Version

In any publish flow (with or without content changes), builders can update the WalkMe runtime by checking Update to the latest WalkMe version.

If this option is selected:

• A warning message appears before publishing
• Confirmation is required to proceed

If the update fails, an error message is displayed and diagnostic events are sent to WalkMe Support for investigation.

Technical Notes

Runtime updates and troubleshooting

• Runtime update actions are logged per environment
• Failed runtime updates generate informative events that can be reviewed by WalkMe Support

Permissions and governance

• Updating the WalkMe runtime version is a permission that can be revoked
• Runtime updates can be restricted so that only specific Admins are allowed to perform them

Preview behavior

• Preview Latest always loads plugins and customizations from the Preview environment, regardless of the selected environment (Production, Test, etc.)

Limitations

• Parent-child accounts are not supported in Enterprise Mode
• Any new WalkMe runtime file added to an account is treated as a version change and will not be included in publishes until the runtime version is explicitly updated

Operational considerations

• If new content is created and published without updating the runtime, some content may not function as expected if the current runtime does not support it
• Using preview capabilities and reviewing Technical Release Notes can help identify compatibility issues before publishing

Some security auditing requirements can be addressed using Enterprise Mode and Self-Hosted accounts. For additional guidance, contact WalkMe's Security team.