All admins will now be able to assign two different permission levels for any given resource: (1) "use," which allows an editor to write queries with that resource and (2) "edit," which additionally allows an editor to modify the resource's configuration.
Previously, admins had minimal control over permissions to resources — any resource permission granted at a group level would allow members of that group to modify the configuration of the resource. We know configuration for some resources can be sensitive and complex to change, so we've shipped these new permission levels to give admins more control over their user's access.
Additionally, to allow editors to create new resources or delete existing ones, admins can assign a group to have “universal access” at the “edit” level. As always, a “viewer” of an app (e.g. no edit permissions) can still view and use an app that leverages a resource for which they do not have explicit permissions granted.
These new resource permissions are available to all admins across Pro+ plans. Drop us a note at firstname.lastname@example.org to let us know how they're working for you!
Fixes and improvements
- Added a new Progress Bar component with an indeterminate state
- Added a new scalable Progress Circle component
- Fixed local storage dependencies such that values nested inside a third level now trigger updates correctly (e.g. localStorage.values.x.y)
- Fixed dynamic height for direct children of Modules and Modals
- Removed inconsistent right panel behavior in favor of the pop out code editor
- Updated the Divider component to support an optional text label
- Added the ability to see tables that are related to your query in the query editor's schema browser
- Fixed the visible scrollbar on single line, fixed height Text components
- Fixed an issue where transformers do not run on page load if they depend on disabled queries
Check out this guide to see the on-prem versions and their release notes. These features will be rolling out to on-prem customers in the next few weeks.