You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
FOUR-34462: Show Designer asset cards and actions according to permissions - #9180
Users with only View Collections and List Collections permissions can open Designer, but the Assets section and Collections card are hidden. Sign in as a non-administrator with those permissions and open Designer to reproduce the issue.
Solution
Include Collections and FlowGenie permissions in the data passed to Designer assets.
Show each asset card only when its package is available, if required, and the user has its view or create permission.
Show listing and creation buttons according to their respective permissions. Server authorization remains unchanged.
How to Test
Browser validation passed with a non-administrator holding only View Collections and List Collections: only the Collections card appears in Assets, View All Collections opens the list, and New Collection is hidden.
Compiled Vue rendering checks passed for view-only, create-only, and combined permissions across all seven asset types, as well as no permissions, full permissions, missing packages, and button visibility.
Vite build passed.
Repeat the browser check with permissions for another asset and with an administrator to confirm the corresponding cards and actions remain available.
Medium Risk
Changes authorization UX in Designer; server-side checks are unchanged, but misconfigured permission strings could hide or show wrong asset actions.
Overview
Designer Assets now respect per-resource permissions instead of a fixed allowlist and package-only filtering.
Each asset definition gets a resource key, and cards render only when the package is present (if needed) and the user has view-{resource}. View All and New actions in AssetButtons are shown separately via canView / canCreate props passed from Assets.vue. The Designer blade template also passes FlowGenie and Collections permissions into the assets component so those cards can appear for limited-role users.
Reviewed by Cursor Bugbot for commit 52768a3. Bugbot is set up for automated code reviews on this repo. Configure here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue & Reproduction Steps
Users with only View Collections and List Collections permissions can open Designer, but the Assets section and Collections card are hidden. Sign in as a non-administrator with those permissions and open Designer to reproduce the issue.
Solution
How to Test
Related Tickets & Packages
ci:deploy