Controlling Access to Data

Each field in your application is associated with a privilege section. This makes the field available to users based on their privileges. For example, users assigned to a certain role may be able to view fields in the User and Manager privilege sections, but they can only update fields in the User section.

Privilege sections play an important role in form design, but custom forms offer the flexibility to organize fields any way you choose without compromising security.

You can:

Organize fields based on their privilege sections
Create custom forms based on quick forms, and do not move fields from visual sections that differ from their privilege section.
Organize fields in visual sections
Move field controls to a visual section, which may or may not be associated with a privilege section. In this case, user privileges determine if the field is visible. For example, the Owner field might be associated with the Manager privilege section, but you can move it into the Standard section on the form. In this case, users who have privileges to the Manager section would see the Owner field in the Standard section, but users without these privileges would not.

This applies to visual sections with similar names to privilege sections and to independent containers, such as a tab control. For example, you can add a tab control with the label Backlog Info and place a field from the User field privilege section within that tab. The field is only visible to users with privileges to work with User fields.
Organize fields in both privilege and visual sections
Create custom forms with auto-sections, and move some fields to visual sections that differ from their privilege section, while enabling the rest of the fields to be automatically placed in their respective privilege sections.

Note: Fields added to your application or auxiliary table are automatically added to custom forms with auto-sections. As you add fields to your application or auxiliary table, you should review your custom forms to ensure the field appears correctly to users.