Skip to main content

Changelog

Updates, changes, and improvements at Retool.

Retool no longer supports Gemini 1.5 Pro. Gemini 2.0 Flash will be used instead.

Cloud customers on all plans can now submit breakage reports from inside the product to report regressions, breakages, and potential incidents on the Retool platform.

The breakage form is available by clicking Report a breakage from the following locations:

  • The Apps and Resources landing pages, by clicking the chat button on the bottom right corner of the screen.
  • The App IDE, by clicking the Help button in the status bar.
  • The resource configuration pages, by clicking the Help button in the status bar.
  • The Query Library, by clicking the Help button in the status bar.

After you submit a breakage report, you will receive a confirmation email with a ticket number.

The Fullstory integration for session replay is now generally available.

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.

Free and Team plan users can now create public links to share apps externally. Anyone with a public link can access the app, so this option should only be used for apps that don’t require authentication or contain sensitive data. Public links were previously limited to the Business and Enterprise plans.

If your instance is self-hosted, reach out to your account manager or the support team and request access to public links.

You can now use the Copy as Markdown button on most pages of the Retool documentation to copy the contents of the page to your clipboard in Markdown format. This feature is intended to give you easy access to a version of the content that you can paste into an LLM for more accurate answers to questions about Retool.

Retool now supports managing permissions using role-based access control in public beta. You can create roles with granular permissions so groups can manage certain organization settings without full administrator access.

Role-based permissions offer much greater access control than Retool's existing group permissions functionality. For example, a Design team may need access to your organization's branding settings to ensure the Retool organization follows branding styles and guidelines. Rather than give the team members admin access, role-based permissions allow for granular control over what specific settings they can access.

Once you configure the necessary roles to control access, you can apply them to any number of groups. Retool will eventually transition away from per-group permissions to role-based access controls as the method with which you manage permissions.

To enable this feature, navigate to Settings > Beta and enable Permissions v2.