Skip to main content

Changelog

Updates, changes, and improvements at Retool.

Refer to the stable and edge release notes for detailed information about self-hosted releases.

The object permissions feature is currently rolling out to cloud instances. It is not yet available on self-hosted instances.

Retool now supports object roles—a new role type that grants groups Use, Edit, or Own access to specific apps, workflows, resources, and agents. Object roles are separate from organization roles, which control access to admin settings like billing and SSO.

When you create an object role, you set an access level for each object type and choose how the role applies:

  • Universal access—The role applies to all current and future objects of that type across the organization.
  • Individual access—Access is scoped to specific objects or folders, which you define when assigning the role to a group.

Object roles are assigned to groups from the Groups page. Once assigned, all members of the group inherit the role's permissions. You can view a group's or user's full object-level access from the Object permissions tab on their detail page in Settings.

Updates to organization roles

As part of this launch, organization roles have been updated to cleanly separate admin settings access from object-level access. The Create Role button on the Roles & Permissions page is now a dropdown where you choose between creating an object role or an organization role. A filter control on the roles list lets you view all roles, object roles only, or organization roles only.

To get started:

  • Object roles—Understand how object roles work, including universal vs. individual access and folder inheritance.
  • Create an object role—Step-by-step instructions for creating and managing object roles.
  • Organization roles—Updated UI for managing organization roles, including a new role type selector and filter controls on the Roles & Permissions page.
  • Assign roles to groups—Assign object or organization roles to groups.

You can now trigger workflows from functions in the new app builder. Converting classic apps that trigger workflows is now supported as a result.

To trigger a workflow from your app, open the Chat tab and prompt your agent with the workflow's name.

Update my app so that the Customer Feedback table retrieves data using the Retrieve Survey Feedback workflow.
Create a new app that tracks our quarterly sales KPIs. For the data, use the Calculate Conversion Rate workflow as well as the lifetime_value and quota_attainment tables in @Retool Database.

The triggered workflow is run on behalf of the app's authenticated user.

Classic apps that include custom components and organization-level themes can now be converted to the new app building experience.

To support custom components, the agent investigates the custom component and recreates it in the converted app with as few changes as possible.

To support classic organization-level themes, the agent applies the same style, color, and typography to the app as were represented in the organization-level theme. The agent does not create a new organization-level theme that applies to apps created with the new app builder.