Skip to content

FOUR-34462: Show Designer asset cards and actions according to permissions - #9180

Open
eiresendez wants to merge 2 commits into
developfrom
bugfix/FOUR-34462
Open

eiresendez wants to merge 2 commits into
developfrom
bugfix/FOUR-34462

Conversation

@eiresendez

@eiresendez eiresendez commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

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

  • 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.

Related Tickets & Packages

  • FOUR-34462
  • Core Designer UI; integrates with Collections, Data Sources, Decision Engine, and AI packages.

ci:deploy

@cursor

cursor Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

PR Summary

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.

@eiresendez eiresendez self-assigned this Nov 18, 2026
@nolanpro

Copy link
Copy Markdown
Contributor

QA server K8S was successfully deployed https://tenant-1.ci-d3db2bf3c1.engk8s.processmaker.net

@eiresendez
eiresendez requested review from mcraeteisha and removed request for CarliPinell November 18, 2026 22:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants