This is a common problem with a list view that is filtered/sorted/paginated (see this answer for a diagram).

In general, any records added to such list (and in some cases even records modified) will require data reload. If you wish to focus users on the new set of records, there is also an issue that the previous view settings will be lost although these might still be important for the user.

So whichever way you do it, there will be some possible issue showing these new records on the existing list view.

Sometimes, solutions like 2 make sense - if no other use case suffers from the list view data being changed after an add action.

But the solution you gave as 1 - showing these records in a separate place is less likely to work better, all use cases taken into account.

This is a common problem with a list view that is filtered/sorted/paginated (see this answer for a diagram).

In general, any records added to such list (and in some cases even records modified) will require data reload. If you wish to focus users on the new set of records, there is also an issue that the previous view settings will be lost although these might still be important for the user.

So whichever way you do it, there will be some possible issue showing these new records on the existing list view.

Sometimes, solutions like 2 make sense - if no other use case suffers from the list view data being changed after an add action.

But the solution you gave as 1 - showing these records in a separate place is less likely to work better, all use cases taken into account.