Please provide more context -
https://access.redhat.com/documentation/en-us/migration_toolkit_for_applications/6.1/html/user_interface_guide/assessing-and-analyzing-applications#mta-web-creating-custom-migration-targets_user-interface-guide

Please add an introductory paragraph using the Konveyor feature:

Custom Migration Targets

Large-scale modernization and migration projects are often led by a group of architects who work together as a steering team and a series of third-party factories that do the transformation at scale. It is not uncommon for third-party factories to provide developers with a very focused set of skills, which makes it difficult and expensive for them to learn new tools and technologies, especially if they are complex. One of the key concerns of the MTA project is to provide differential value at each stage of the modernization process. This includes making sure we lower the barrier for these developers to take advantage of the capabilities of the MTA tool.

Through interaction with different focus user groups in the field, it has been discovered that configuring custom rules on each analysis run can be cumbersome and does not scale well when dealing with third-party factories. The purpose of this enhancement is to provide an abstraction layer for these users, hiding away the complexities of custom rules configuration by exposing them as custom migration targets managed by advanced users.

Motivation

The documentation of this enhancement must provide the following information:

• Developers do not need to understand how custom rules work to take advantage of them.
• Architects can create custom rules on their own and ensure that third-party developers use them in a straightforward way.
• Analyses can be performed faster when dealing with a series of well-known custom technologies that are widespread across the entire application portfolio in an organization.

Goals

• Lower the barrier for the usage of custom rules at scale.
• Abstract unskilled users from the complexities of custom rules development and configuration.
• Simplify analysis configuration and execution.

Administrator|

Architect or Migrator |

Documentation Personas 

• Administrator: The administrator for the tool that has access to some application-wide configuration parameters that other users can consume but not change or browse.
• Architect: A technical lead for the migration project that can create and modify applications and information related to them.

• Migrator: A developer who should be allowed to run analysis, but not to assess, create or modify applications in the portfolio.