AVEVA™ PI System™ Feedback Portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Add a new idea Subscribe
Status No status
Product AVEVA™ PI Server
Categories Security
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

User rights for viewing analytics

In many cases analytics should not be visible to everyone having right to view an AF-Database. Should be possible to direct whom should have view access to analytics. This is an extension to the obivious right to change analytics :)
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    This is existing capability. You can decide who can read/write analyses by making the appropriate changes using something like PI System Explorer. Please see attached screenshot
  • Brent Bregenzer
    Reply
    |     Aug 20, 2022
    In response to Stephen Kwan, "This is existing capability.  You can de..." Hi, Steve. In PSE User guide, it states: "The following objects always have Read permission regardless of their security settings, so long as the logged-in user has Read access to the PI System and the PI AF database... -Analysis template -(list of other library objects)" Is there a way around this so users with read access to elements, attributes and their templates cannot see analysis templates on the element templates?  In my testing, explicit Deny does not seem to override this, but hopefully there is another way. Another interesting observation from my testing:  Analysis data reference attributes don't seem to resolve when the user doesn't have read access to the corresponding analysis: I'm not sure there is a way around this other than to use a PI Pt DR for the output.