Skip to main content
Question

Action Flow Usage Restriction for Non‑Usage Dashboard Users.

  • April 24, 2026
  • 1 reply
  • 34 views
Hemanth R
Level 2
Forum|alt.badge.img+1

Hello everyone,

We currently have a functional dashboard used for daily operations, which includes several Action Flows. These Action Flows are intended only for a limited set of users who actively use the dashboard on a daily basis. To restrict access for other users, I attempted creating a duplicate version of the dashboard without the Action Flow functionality. However, maintaining two versions of the same dashboard has become operationally expensive and difficult to sustain. Could you please suggest if there is a way to restrict Action Flow functionality based on user access or role, without duplicating the dashboard?

Thanks in advance.

    1 reply

    gagan1
    Level 10
    Forum|alt.badge.img+3
    • gagan1
    • Level 10
    • April 29, 2026

    ok so honestly what you can do here is instead of maintaining two full dashboards just create two separate views inside the same package one with the action flows and one without and then assign different user groups access to each view that way you have one package to maintain not two whole dashboards which is way less painful.

    and on top of that in admin and settings under automation permissions you can actually control which specific users or groups can execute an action flow at all so even if someone ended up in the wrong view the backend would block them from running it anyway. the conditional hiding of buttons based on who is logged in is not really supported natively in studio at runtime which is the annoying part but the two views inside one package approach gets you pretty much the same outcome without the overhead you are dealing with right now

    I hope this helps 

    Gagan
      Community Code of ConductAccessibility statement