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 Vision™
Categories User Experience
Created by Guest
Created on Sep 29, 2022

RELATED IDEAS

Have the Unassigned AF Identities match the identities permitted to use PI Vision

When sharing a display, the Unassigned AF Identities are taken from the complete pool of AF Identities.

This list should match the User Access Levels of the PI Vision Admin website. Likely the sum of Publishers and Explorers. If an Identity cannot make or see displays in the whole PI Vision, it shouldn't be possible to give access rights to the Identity on individual displays.

This will easily allow to remove from PI Vision all the AF Identities for services (Asset Analytics, RTQP Engine, etc.) that are irrelevant to PI Vision users. In that respect, it is more about User Experience than Security.

Display access ...
Display access and Admin website - Copy.png
Open full size
Display access and Admin website - Copy.png
  • Attach files
  • Laura Morris
    Feb 4, 2026

    I agree, this presentation adds friction in the adoption of PI Vision and is confusing for users. As a requirement in configuring the PI System there are service account Identities that must be created. There's no reason for standard users to see or known anything about these users.

    There are also prebuilt identities that may not actually have any mappings, but 'sound like' the people that a user wants to share with. If using the unassigned identities list as designed, users may easily select an ID only to find it was not at all who they wanted to share with.

    Support adding restrictions as any owner/creator can update display settings, but they shouldn't be exposed to the full pool of IDs that admins see/create. Thanks!

    Reply