Changes

Please note we take a most restrictive approach when it comes to permissions, so if you set one role to deny something, it will supersede all other permissions. This means if a user has 3 roles, and 2 roles have permission to do something but the third role does not, the user will not be able to do that action. So as a general practice it is better to add permission then to deny permission on a role. This way, the more roles you have, the more you can see and do in the system.

Before you start building a portal, plan out what each user will need to see and do in their portal.

Let’s use a grant applicant as an example. The grant applicant will likely need to be able to:

Now that we have User Roles and we know what our users are going to do in the system, we can decide where we are going to create the portal.

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. If you take this path, assets will not be shared and users will need to flip between roles.

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 harder to maintain and provides a worse user experience, given people may have multiple roles (example I am an employee and grant manager).

The portal header consists of 3 elements: the Logo, the user menu and the main menu.

There are also two styles of header, the default and the compact.

We recommend creating sections in single column as they will render best on all screen sizes and this provides a better experience for people using assistive technology.

To create a page for your portal, navigate to '''Global Settings''' > '''Users''' tab > '''Portals''' and edit the desired portal. Under the '''Portal Page''' title bar, click the plus button to add a portal page. Give your page a '''Name''' and '''Caption'''. If you don't want to display this new page in the top header, toggle off the setting '''Display As Header Link'''. You can still reference this page in a shortcut link, but it will no longer appear in the header.

==== ====

Beyond choosing the layout, you can choose how you want your sections to look.

There are three theme options: Default, White paper, and website. You can mix and match these themes at the page level. So, you could have a home page that uses the website theme and then another page for applications in progress that uses the white paper theme. It's easy to flip between themes and see which will work best for you.

====General tab====

{| class="wikitable"

=== ===

Once you have created a main menu link and set it to sections, you have a number of section options. Below is an overview of each section option.