A portal may open a report or authentication step in a second window. When nothing appears after one deliberate click, inspect Chrome before clicking repeatedly. Several queued actions can make it difficult to tell which window belongs to the current request.

Check the blocked-window evidence

Keep the original portal tab open and look for the blocked pop-up indicator in the address bar. If it is present, select it and inspect the offered link. Compare its destination with the service’s expected domain or documented sign-in provider. An unexpected domain deserves verification with the service owner before entering credentials.

Chrome lets you select the individual blocked link. Use that narrow option for a one-off document when possible. Check whether the resulting window contains the expected report, account or confirmation, and whether returning to the original tab completes the intended process.

If there is no blocked-window indicator, record the button’s result and any message on the page. The failure may belong to the application itself. A blanket pop-up allowance is not evidence that this browser control caused the problem.

Decide whether an ongoing exception is useful

For a recurring, verified workflow, Chrome offers a continuing allowance for pop-ups and redirects from that site. Read the displayed site before accepting it. Keep the general browser default as a separate decision; a single reporting portal does not establish a need for unrestricted pop-ups elsewhere.

Test again with a harmless document and record the result. Later, review the site under Settings, Privacy and security, Site settings, Pop-ups and redirects. Remove or block an allowance that is no longer needed.

Work or school policies may control this setting. Give the administrator the portal address, blocked destination and failed step rather than trying to bypass management. The acceptance check is the completed portal task, not merely the appearance of any new window.

Sources: Chrome documentation.