Updates, changes, and improvements at Retool.
Organizations on the Business or Enterprise plan can now restrict users from accessing specific app pages with per-page permissions. When configuring a permission group, you can now also specify permissions for each page.
This feature is currently rolling out on Retool Cloud. It will be available to organizations on Self-hosted Retool in a subsequent edge release.
Retool has rolled out unique identifiers (UUID) for app pages. If you use Source Control, Retool recommends that you create a new branch with no changes and push it to Source Control. If you use Retool Cloud or self-hosted Retool 3.191-edge or later, Retool automatically creates a migration commit to add UUIDs to each page. Once you merge this commit, you can successfully configure per-page permissions on your protected app.
If you are working on more than one branch before the UUID addition in version 3.191-edge, Retool runs the migration on each of those branches, and the branches will end up with different UUIDs. Make sure add UUIDs only once, do not override the UUIDs on the main branch after adding them. Doing so results in the inability to set per-page permissions, because the IDs initially set on main are the ones that Retool will use.
Retool now supports Drafts, a tab of the Apps landing page that provides a personal folder for each standard user to develop and test apps. Only you and organization admins have access to view or edit apps that you create in this section. This feature is useful for organizations where creating applications and folders is restricted, because admins don't have to give users explicit permission to create apps in their Drafts.
The availability of the Drafts tab can be managed by admins in Settings > Beta.
The Drafts tab is currently rolling out on Retool Cloud and will be available on the next edge release of self-hosted Retool.
Resources now have additional permission levels. This make it easier to build apps with sensitive data in a secured way.