AVEVA™ PI System™ Feedback Portal

Welcome to our new 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 Vision™
Categories Security
Created by Ryan McErlean
Created on Aug 19, 2022

RELATED IDEAS

Have displays automatically inherit folder permissions

As a PI Vision admin, I would like displays to automatically inherit the permissions of their parent folder so that permissions are set automatically when users save displays to the appropriate folder. Currently permissions for folders and displays are not tied together but they can be propagated manually using the 'Propagate permissions' checkbox in the Folder Settings dialog.
  • Attach files
  • Albert Abeijon
    Reply
    |     Jul 26, 2023

    https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=000028902

    The above article mentions:

    "To make changes to a display in a folder users need write permissions on both the display and folder."

    https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=000041790

    The above article mentions:

    "Display has been shared with Read & Write permission to their mapped identity"


    Both articles suggest that display permissions can be adjusted within a folder. In reality, once a PI Vision display is in a folder, whatever permissions that display have get ignored and the folder permissions are used instead.


    This prevents us from allowing read-only access to some displays in a folder, and write to others. It is currently an all-or-nothing permission set once a display is in a folder. Documentation should make this clearer.


    The ideal scenario is that once a display is created in a folder, it inherets the security of that folder. Permissions can later be set on the display level even when in a folder.

  • Matthew Del Bonta
    Reply
    |     Sep 22, 2022

    This is a critical item for several of my customers. Enabling the functionality will make wide adoption and utilization of PI Vision (migrating from PB) much easier and efficient. Thank you.

  • Guest
    Reply
    |     Aug 19, 2022
    Only a PI Vision administrator can use the "Propagate permissions" checkbox on the top level folder to update the permissions on all the displays in that folder. Currently a user who has R/W access to the folder cannot even see who the top level folder is shared to. I would like to see this more like the windows files system security. If a display is "Save As" from the home folder to a container folder (copy created) then the display should initially inherit the share settings from the container folder. If a display is moved from the home folder to a container folder then the permissions should stay as they have originally been set.
  • Matthew Nitz
    Reply
    |     Aug 19, 2022
    The fact that there isn't at least an option for displays to inherit permissions from the folder is highly problematic. Having a display saved by default with different permissions than the folder it is in is completely different behavior than a file type structure PI Vision emulates and as such is extremely unintuitive to users. I have tried to spread this information to users at the site, but you are never going to have all people remember it 100% of the time. So as the administrator I end up going through our folders on some periodic basis to check if there are some displays that weren't shared correctly and doing it myself rather than having it happen automatically. There is another level to this where it would be nice to have an option to set a folder to not just initially set permissions for the display to match the folder but LOCK them to do so. Most of the official folders we have set up we don't want people in any cases having displays just for personal use saved in those folders anyway, so if we could just ensure that never gets changed it would be extremely helpful. Again, this doesn't have to be something you require for every folder, just an option we could enable to a folder level, or at least an option on the server so we could switch all our folders to it if desired.