Improvements to source control on Workflows are now generally available on Self-hosted Retool 3.200.0-edge and in the upcoming stable release. The following features are now supported for all users on Enterprise plans:

Retool made several improvements to the usage of Source Control with Retool Workflows. The following features are now supported on Enterprise plans:

• Branched changes. You can now make changes to workflows using branches. Previously, all Source Control changes on workflows were branchless.
• Multi-element branching. You can make edits to workflows on the same branch as edits to apps, modules, and Query Library queries.
• Collaborative branches. Multiple users can commit changes and merge pull requests on collaborative branches.

Retool can record user behavior and interactions with apps using Fullstory. When enabled, data about user interactions with apps are reported directly to Fullstory for you to review in detail. You can then analyze app analytics, evaluate impact, and review interactions with session replay. This integration is useful for monitoring user activity across different apps, and using advanced analytical tools like heatmaps and funnels to identify usage patterns, debug errors, and improve the overall user experience.

If your organization uses Source Control, Retool sometimes creates an automatic commit, called a catch-up commit, which keeps your branches up to date. If you want to ensure that developers in your organization retain complete control of changes within their feature branches, you can now disable catch-up commits using the following steps:

1. Navigate to Settings > Source Control and click the Edit Settings button on the top right.
2. Toggle on the Disable auto catch up commits setting.

To avoid issues with catch-up commits and other merge control mechanisms, refer to Retool's Merge conflict prevention strategies.

Retool now supports the Login Attempted Retool Event, which triggers after a user authenticates and before the login process is complete. You can use Login Attempted to trigger a workflow and execute custom logic, such as modifying user data or querying external resources.

Choose to present users with an error message, or redirect them to an app or URL.

You can only attach one enabled parent workflow to this Retool Event. Retool recommends that this logic remain lightweight, because this workflow runs synchronously in the login flow and blocks users from accessing their Retool account until the workflow finishes.

Retool has updated the built-in usage analytics with an improved experience that now organizes different data sets into tabs. These changes streamline the amount of data presented so that you can more easily focus on the analytics you need.

Retool surfaces a variety of usage analytics for you to monitor:

• Aggregate app usage over time.
• Aggregate active users over time.
• Individual app usage summaries.
• Individual user usage summaries.

The Usage Analytics feature is available for cloud- and self-hosted organizations on the Enterprise plan.

Enterprise users can now protect organization-level themes using Source Control. This enables you to safely replicate organization-level theme configurations across multiple instances of Retool. You can use protected themes with any of Retool's supported source control management (SCM) providers.

Internationalization (i18n) is now in beta for organizations on the Enterprise plan. This allows you to localize Retool app content and data.

This beta is available on Retool Cloud and self-hosted deployments running Retool 3.38 or later. Contact your Retool account team to request early access.

Enterprise plan organizations on Retool Cloud or with a self-hosted deployment running Retool 3.38 Edge or later can connect and send all audit log events to Datadog.

We're releasing a new wave of Retool platform capabilities to provide greater flexibility and governance over how you organize your teams, secure your data, delegate permissions, and more.

We're going even further on foundational platform features (SSO, RBAC, environments, Source Control, audit logs, and multiple hosting options), adding:

• Spaces: Independent workspaces for teams to manage their own apps, permissions, resources, connections, and git repos—all while sharing core infrastructure with other teams.
• Platform APIs Programmatically manage the Retool platform with robust API endpoints to manage workspaces, provision users, assign permissions, organize apps, and more.
• Extended permissions: Grant data-level access permissions for resources in each environment, ensuring that applications built in Retool are secure by default
• Orchestrated governance: Create automated workflows and alerts that trigger whenever users are created, sign up, request access, and more.

A line of sight into your business operations is critical to decision-making as you scale. With Usage Analytics, Retool admins have a single place to:

• Monitor all app and user adoption.
• Gain insight into aggregate usage to effectively manage teams and apps.

Usage Analytics is available to all Cloud and Self-hosted customers on the Enterprise plan. You can access it in your Organization settings.

Usage Analytics for Self-hosted deployments requires Self-hosted Retool v2.113 or later. Check out the docs to enable Usage Analytics.