Uipath Marketplace
MarketplaceListingsSolutionEnquero - File Path Access Validator

Create your first automation in just a few minutes.Try Studio Web

Enquero - File Path Access Validator

Enquero - File Path Access Validator

by Enquero Inc





back button
back button
next button
next button



Handle the file path pre-validation need and the access permission from the beginning of a BOT development cycle.



BOT user is often required to access different physical and network shared file paths for various file I/O operations, especially when working with MS Excel, CSV or PDF files. All such shared directories and sub-directories have access permissions defined through some Group Policy by the IT administrators. In lots of business requirements, the BOT process during its execution is required to access the file paths to read or write files from/to the source/destination address respectively. But in practice, it is mostly seen during BOT development or migration to Test/Production servers, the BOT processing fails when the file paths access permissions are not as expected.

The FilePathAccessValidator workflow is developed using a Windows PowerShell script. The inbuilt Invoke PowerShell activity of UiPath executes the PowerShell script to query Windows Folder objects to list user permission details.

It expects two file paths as inputs: 

  • one to read access permission details
  • other to write output summary in a CSV file.

Further, a username is provided as input to query in the CSV result set. Later, developers can read the permission details from the CSV file to tailor their needs to proceed further in the workflow. In the attached workflow, its usage is also illustrated with a hypothetical use case to query and print the user’s permission details in logs.



The advantages of using the File Path Access Validator include: Query the user access details of the file path (directory, sub-directories, network shared path, etc.) Verify if a given user (say, a BOT user) has any read-write access to the file path or not Most useful when a BOT user's access to the file path(a network shared directory, sub-directories for file I/O operations) needs to be queried and verified after the Init state in ReFramework Reusable across different projects and workflows

Additional Information

Additional Information


Windows PowerShell ExecutionPolicy Windows PowerShell has an inbuilt security setting called "execution policy". Execution Policy determines how (or if) a given PowerShell script can run. By default, PowerShell's execution policy is set to "Restricted", which means the script will not run. You can verify the currently set execution policy by querying on a PowerShell command console as: Get-ExecutionPolicy. It will tell the execution right of the currently logged in user. You need to change the behavior of a PS script execution from the PowerShell command console as: Set-ExecutionPolicy RemoteSigned. You should be able to execute PowerShell scripts then. Else, you can check with your IT team.

Code Language

Visual Basic


Enquero Inc

Visit publisher's page

Trusted Source

License & Privacy


Privacy Terms





Jun 9, 2023

Works with

Studio: 21.10 - 22.10


Silver Certified


UiPath Community Support


Similar Listings