Field-level permissions, as a rule, are not likely to be created as part of an initial design. Rather, it is expected that the Issues page will be created first, and then a need for field-level permissions will be found. At that point, an administrator will go back and either create a new field that is to be restricted to specific roles or restrict an existing field to certain roles. In addition, it is not expected that new roles will be created to accommodate field-level permissions. However, while adding roles to accommodate field-level permissions is not expected, this section describes how permissions are applied to existing fields, creating new fields to be restricted with field-level permissions, and creation of new roles to accommodate field-level permissions, just so that all the bases are covered.
Field-level permissions can be specified by selecting Administration | Project from the FootPrints toolbar, then selecting User Roles under the Roles section of the main frame. At that point, you can go through each of the fields that are visible to that role, one after the other, and set them for that role.
As an alternative, you can select Administration | Project or Administration | Address Book from the FootPrints toolbar, then select Field Maintenance in the main frame. You can then edit an individual field and set the same field-level permission for that field for a variety of roles. Methods for setting permissions are discussed in the subsequent topics.
Field-level permissions are specified differently depending on whether you are creating restrictions for built-in fields or custom fields.