Currently:

Data extraction configuration such as selecting which kinds to extract and defining API level selectors is set in the mapping. This means that the first sync after installing the integration includes only the default kinds and no selectors. The extraction behavior changes only after a user updates the mapping.

Expected:

We would like to move all configuration related to the extraction phase from the mapping to the installation and settings pages. This would allow users to filter data and choose kinds from the API even during the initial installation. It would also improve discoverability of available kinds and filters. This change is also required for the new architecture of the upcoming mapping experience planned for Q1.