Changes

There are two ways in which you can create a portal. You can create the portal on the Common role which is aggregated, meaning assets are shared across multiple roles , or you can create a portal on a single role but if . Iff you take this path , assets will not be shared and users will need to flip between roles.

To use this option, build your portal on the common role. When you create an asset such as a section inside the common role portal, you can permission that asset to be viewable by specific roles. This way you can build an asset like a help link and share it amongst all user roles. If you need to change the help link, you change it in one place and all users will see that change. If a user has multiple roles, they will be able to see and do whatever all their roles have permission to do. Lastly , creating assets on the common role means users do not need to switch between portals using a drop down in the header , as they can always see whatever they have permission to see and do.

This portal configuration is generally not recommended. With this option , you create a portal on each role. So, the applicant portal is built on the applicant role and the reviewer portal is built on the reviewer role. The drawback to this approach is that if you need to create a help link, you need to build it on each role. If you want to change the link you must go into each role to change it. If users have multiple roles , there is a drop down in the header that allows the user to switch between applicant and reviewer portals , but you only see one portal at a time and don’t have access to all the functionality that has been permissioned for you at one time. Although it is easy to understand and configure one portal per role , it is generally is harder to maintain and provides a worse user experience , given people may often have multiple roles.