Taking action after your upgrade

In PI2, user permissions are modular, allowing you greater flexibility in how you control access to sensitive data and tools. Because this permission structure is new, not every user role from Legacy PI is being carried over the same way.

In this section, we’ll cover three steps to ensure you have the right permissions in place for PI2.

3 steps for accurate permissions in PI2

1. Review permissions for Account Admins.

In Legacy PI, Account Admins had permissions similar to the Account Owner. For PI2, this is not the case. The two highest permission levels in PI2 — “Organization Admin” (Account Owner) and “Product Admin” (Account Admin) — differ quite a bit in what they have access to view and do.

Consider who had Account Admin permissions in Legacy PI. Will they need access to all data at your organization? Would you like them to be able to archive records or view cognitive data? If the answer to either question is “yes,” you’ll want to grant these individuals “Organization Admin” access.

2. Reshare jobs/teams with Power Users and Users.

Any Power Users and Users from the Legacy experience will become “Limited” users in PI2. For the most part, these users will have similar access in PI2 to what they had in Legacy.

There’s one major exception: If these users had access to jobs or teams through a folder in Legacy, they will no longer have access to them in PI2.

3. Grant access to Read-Only Users (as needed).

In Legacy, Read-Only Users had very limited access to data. In PI2, these users will lose access to all software modules except for PI Inspire. This will allow these users to continue to view employee data and reports. However, you may find this permission change is too restrictive.