Hello @Nikola Laskowska,

Please merge code to dev branch.
This is the best moment to add more information that can be helpful to prepare release notes.

• Can you prepare short overview of change that can be used in release notes?

• Please provide short GIF that showcase feature.

• If GIF make no sense, can you provide image that highlights feature that can be used in release notes (cropped & annotated)?

Task verified - QA env

Hello @Nikola Laskowska

This is the best moment to add more information that can be helpful for tester.

• What areas are affected?

• What are potential edge cases?

• Was it checked for XSS problems?

• Does change affect security, is new data exposed?

Please attach - Before / After screenshot if possible.

Hello @Nikola Laskowska,
Change was reviewed and approved.
Task is ready to be deployed to QA.
Once it is deployed to QA please move ticket to "To Test"

Thank you!

@Krzysztof Bogdan

@Nikola Laskowska 🏓

@Krzysztof Bogdan comments adressed

@Nikola Laskowska 🏓

Hello [~accountid:],
Task is ready for review.

@Nikola Laskowska please make sure reviewer
have easy access to contend to be reviewed.

If this is code change. Please make sure PR is created.
If this is new documentation, blogpost, etc. Please provide link to page.

current progress: endpoint updated to get only domains, not whole emails + communication between frontend and backend for getting validaton results done, left to do: visual validation handling, code cleanup

Current status: prepared new endpoint which validates if domain is on the provided list. API calls works properly for attached cases.

for case with empty array false is also sent

information about that we are not supporting most popular email domains should be added to tooltip → or any email address from domain

when one of email domain from list is added then we should display error (use angular input form error mechanism) that we do no support sharing with most popular email domains to avoid spamming users