Bring back the "View Missing Dependencies" when assigning permissions

With the new layout of the group permissioning, we have lost the ability to see missing dependencies such as when a group has permissions to an app, but does not have required permissions to one or more of the resources used by that app. Yesterday we had to create a new group and assign it access to one of our Retool Classic apps, this meant we had to pull up the app and the group permissions side-by-side and go query by query and assign permissions to each resource individually. Even with the new retool AI apps, we would still have to open the app and look at its resources, then go to the group permissioning and assign permissions to the correct resources. One oversight means that the users would get an error message and we would have to fix their permissions.

This feature was on available on the old group permissioning, but has been removed in the new system. Please add this back.

Summary

With the new group permissioning layout, the previously available ability to surface 'missing dependencies' — a warning when a group has access to an app but lacks the required permissions on one or more resources that app uses — has been removed, forcing manual, resource-by-resource cross-referencing when configuring a group's access.

AI Response

This is logged as a feature request, and no existing corroborating report or workaround that restores the automated 'missing dependency' detection surfaced in the Community. In the current model, app access and resource access are permissioned independently, and resource permissions must be granted per environment, so a group needs explicit Use access to every resource an app references. As a manual check, the documented 'Groups' and resource-permissions workflows under Settings > Groups can be used to confirm each required resource is granted alongside the app. Adding supporting detail or votes to the request helps prioritize it.

Sources

:bookmark: Manage permissions for resources | Retool Docs
Confirms resources are permissioned independently and per environment, which is exactly the resource access that must be granted manually for every resource an app depends on.
:bookmark: Groups | Retool Docs
Documents the current Settings > Groups workflow for configuring per-object app and resource access when assigning group permissions.

The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a :heart:, :+1:, or :-1:. Or by marking this post as the "Solution"! Let us know if you have any feedback here. :rocket: