Recently updated to v5 and created a script that users have access to in the portal. The script has a file parameter so the user has to upload a file in order to run the script property. The problem is when a user uploads a file it appears to work on their end but not actually upload, the script pauses and requests feedback because nothing was uploaded. When testing under my admin account it works without issues so Im wondering what permission I need to give to my users in order to make this work?
Thank you very much for contacting Ironman Software!
My name is Ruben Tapia, a support engineer in charge of request #CaseNumber. I reviewed the behavior you described in PSU 5.6.11 where admins can upload a file for a script parameter of type [File], but non-admin users appear to upload and then the script runs as if no file was provided.
In PowerShell Universal v5, this is most commonly related to role and permission assignments. As a quick isolation test, please temporarily assign one impacted user the built-in Execute role and retest the upload. If it works, we can narrow down to the minimum permissions required, including ensuring the user or their role has execute permission on that specific script.
If the Execute role does not change the behavior, the next step is to confirm whether the upload request is being rejected. Please share:
• PSU system log entries at the exact timestamp of a failed upload
• A screenshot (or export) of the user’s assigned roles and the script’s Permissions configuration
• Browser DevTools Network capture for the upload request (looking for 401/403 or other failures)
For reference, [File] parameters should be delivered to the script as a PSUFile object.
Thanks for the reply. Once I tested with the execute built in permission I found I had to create a permission giving the custom role the automation/execute permission in order to allow them to upload files despite being able to still run the script previously.