Get-PWDocumentsBySearch : Not logged in as a ProjectWise Administrator.

A ditto for me. This will result in the PowerShell functions becoming absolutely useless. I am using PowerShell to produce dashboard reports from ProjectWise data (which are not available from Project Insights) and as this is just reporting data that is in ProjectWise and not changing anything, does not need Admin login rights. I don't have an Admin log in, and so far have not needed one.

Please do not make the assumption that PowerShell is only / should only be used for server administration tasks - there is far more to its capabilities and use than that.

Given Bentley have pushed PowerShell at us as a way of accomplishing our dashboard reporting (which were very well received at the recent ProjectWise LEARN Conference) for accessing information that ProjectWise can't otherwise, if you are not prepared to open these functions back up again to non-Admin users, then I guess I will just have to push my reporting requirements back to Bentley to solve.

Brian - +1 for including the Restricted Admins 

As an Administrator for a number of large systems I am in full support of the Admin only usage.

The PowerShell cmdlets are not yet supported under the SELECT agreement so they should be used in a controlled manner. I have seen a major outage caused by somebody using a script - even though they were an Admin user!

That said, I can see the benefits of having a tiered approach to security - e.g. PowerShell Admins & PowerShell Users with read-only functions available to the latter - as well as an Audit trail record indicating that an action was run from PowerShell but not at the expense of slowing down the fast development cycle we are getting today.

You can see from the amount of discussion in the Communities pages and at Bentley events that the PowerShell functions have become essential tools for administering ProjectWise and for me personally save many hours of work on repetitive tasks.

Well, we've never really looked at the use case of non-admin users using the PowerShell cmdlets. We actually looked at the use of Open-PWConnection without admin credentials allowing you to use the PWPS_DAB cmdlets to be a bug. I'm pretty convinced non-admin users shouldn't be using PowerShell to manipulate the datasource, and I've made various commitments to internal parties that we wouldn't permit non-admin access.  That said, we will support Restricted Admins in the next release.

Next release will be in a day or two.  We tend to have pretty short release cycles for PWPS_DAB.