Depending on which version of ExtraView layouts are installed with your new installation, different permission settings may exist. These different layouts may be a minimal set of layouts, where you will do most of the customization yourself, or they may be one or more of a series of layouts for “best practices” implementations such as bug tracking or customer support.
The visibility of individual fields or items within your installation may not be quite what you need. Firstly, if you are not certain, note the ADMIN user supplied with all ExtraView installations overrides the security permission settings, therefore if an item is visible using the ADMIN user, it is certain that a permission is not set the way you require. Secondly if you cannot see a field you require or you create a field and do not see it where you expect, check the field has been placed on the appropriate layouts as well as checking that the field has the correct permissions. Other sections of this guide explain all these items, but this is a short list of the permissions that frequently need to be checked and altered on a new installation:
| Security permission key | Purpose |
| AREA.nn | nn is the internal ID of the business areas, and if you do not see a business area you expect, check these keys |
| CF_AREA | Visibility of business areas. This includes the ability to add or edit the list of business areas in administration |
| CF_PROJECT | Visibility of projects This includes the ability to add or edit the list of projects in administration |
| CF_PERSONAL_OPTIONS | Gives the ability to edit your personal options |
| STATUS.xxxxxx | xxxxxx is name of each status value in your installation. If you do not see a status value in a list on the add or edit screens, it is likely you did not give the correct permission to its security permission key |
