ExtraView offers the ability to customize user accounts through a number of pre-defined fields which can be used to add new fields to each user's record. Outside of key fields which are mandatory within each user's record, each of the following fields has a security permission key which can be used to hide or enable the field.
Each of the pre-defined keys is protected with a security permission key, so you can set up different access profiles to the different user fields for different user roles.
The fields that can be customized are shown below:
| Field | Purpose |
| USER.ACCESS_UDF_DATA | This permission key controls overall access to the complete list of user defined fields USER.USER_DEFINED_1 - USER.USER_DEFINED_10 |
| USER.ADDRESS | The two fields that comprise the user's address |
| USER.CELL_PHONE | The cell phone number of the user |
| USER.COMPANY_NAME | The user's company name |
| USER.FAX | The user's fax number |
| USER.LOGIN_ID | An alternative to the User ID that can be used to sign on to ExtraView. Once a user account has been established, the USER_ID cannot be altered as it is used in many places, such as recording who creates and who updates issues. In some organizations, there might be a need to provide an alternative, for example after a company takeover. Also, users may change their name, so this facility allows the user to set up an alternative to their original USER ID |
| USER.LOGIN_ID_ON_ADD | This key controls whether the USER.LOGIN_ID is shown on the Add User screen. This is not typically needed, but is available if necessary |
| USER.PAGER | The pager number of the user |
| USER.START_PAGE | This permission controls the ability of the user to set their start page when entering ExtraView, to a commonly used page such as the Home Page, the Add Issue screen or the Search / Report screen. This is set on their personal preferences page |
| USER.USER_EMAIL_ADDRESS | This is used to control read/write access to the email address of the user. This only has an affect on the update screen for the user. There is always write access to the field when creating a new user |
| USER.USER_ENABLE | Write access is needed to this field in order to be able to enable and disable user accounts |
| USER.USER_FIRST_NAME | When updating the details of a user, this permission key controls read and write access to the field. If there is no read or write access when updating a user, the field is not visible. The field is always writable when creating a new user |
| USER.USER_INTEREST_LIST | Giving read and write access to this key allows each end user to opt-in and opt-out of interest lists to which they may belong |
| USER.USER_JOB_TITLE | The user's Job title |
| USER.USER_LAST_NAME | The user's last name |
| USER.USER_NAMED | This permission controls the ability for an account administrator to set a user to use an available NAMED user license when the system is in MIXED mode. The default for newly created users is that they use a CONCURRENT license. This is not used if you have only NAMED or only CONCURRENT users in your installation |
| USER.USER_PASSWORD_MANAGEMENT | This controls the ability to expire users' passwords, and the time interval information associated with passwords, such as the password expiration interval and the number of days until the password expiry. Write access is needed to alter these fields |
| USER.USER_SECURITY_PASSWORD | The user's password |
| USER.USER_DEFINED_1 - USER.USER_DEFINED_10 | These are ten user defined fields for the user record. You can set the security permission to any one of these to read and write, and alter the title of the field in the data dictionary as needed. This provides the capability to have ten user defined text fields for your installation |
| USER.WORK_PHONE | The work phone number of the user |
