You can add and remove users from an ALM project. You can also assign users to user groups to restrict user access privileges.

You can assign privileges to user groups by specifying permission settings. This includes specifying transition rules and hiding data.

You can modify system fields and add user-defined fields for project entities.

You can add requirement types to your ALM project and define which fields are available and which fields are required for each requirement type.

You can add custom field lists to a project. A field list contains values that users can enter in system fields or user-defined fields.

You can use cross project customization to apply customization from a template project to one or more linked projects.

You can customize criteria and criterion values for risk-based testing, and customize default testing efforts and testing levels.

You can write workflow scripts to customize the ALM desktop client user interface, and to control the actions that users can perform.

You can set up automatic mail notification rules to inform users using email about defect field changes.

You can activate alert rules to instruct ALM to create alerts and send email when changes occur in the project.

You can create and customize the project planning and tracking (PPT) KPIs.

You can create and design report templates that project users can assign to template-based reports.

You can configure Business Process Testing and BPT Packaged Apps Kit.

You can create business views which can be used as a basis for creating reports in the Analysis View module.

You can configure settings for working with Sprinter for manual testing in ALM.

You can customize the settings of a Digital Lab enabled project by overriding the default Digital Lab configurations defined at the site level.

You can perform the necessary customizations to work with Application Lifecycle Intelligence.

Applicable only if you enable the ALM Dev Extension. For details about IDE Connector Customizer, see IDE Connector Customizer add-In.

The default option.

When a user session expires and the user reconnects, customization reloads.

We recommend that you use this option only for critical changes that must be made available to users as soon as possible. Limiting major changes enables users to quickly reconnect without reloading customization. For example, you might use this option when adding a required user-defined field.

When a user session expires and the user reconnects, customization does not reload.

If at least one major customization change has been made since the last login, customization is reloaded when a user reconnects. This includes all major and minor customization changes that have been made between the last time the user logged in and the current login time.