For a long time, the web browser has been a pass-through. You look something up, skim a page, copy a few lines, and then move into email, Word, or PowerPoint to actually do the work.
One example of how this pattern is beginning to change is Copilot in Microsoft Edge. This is not a recommendation for a specific browser, but an illustration of a broader shift: browser-based AI can support early sense-making tasks, such as summarizing information or extracting key details, directly where people are already reading.
At the University of Iowa, the use of any AI tool—including browser-based tools—is optional and situational. The University does not require or prefer Edge as a browser. Tool choice depends on the task, the data involved, and the level of review required.
What Copilot in Edge can and can’t see
If you’ve tried Copilot in Edge, you may have noticed that it is fairly restrained by design.
- It does not see all of your open tabs.
- It does not scan your browser history.
- It does not look inside systems that require you to log in.
Copilot works only with the page you are actively viewing, and only when you explicitly ask it to summarize or extract information from that page. Public web pages are generally accessible. Private systems and authenticated portals are not.
These boundaries reduce the risk of pulling sensitive information into an AI prompt by accident and help keep control with the person using the browser.
Why this still changes how work begins
Even with those boundaries, something practical shifts when light AI assistance is available directly in the browser.
The work that happens before drafting can become lighter. Instead of reading a long page and deciding what matters, you can ask for a short summary. Instead of scanning for dates or requirements, you can have them listed clearly. Instead of starting with a blank document, you can turn what you’re reading into a rough first pass.
At the same time, browser-based AI is not a good fit for everything. It is not designed for deep analysis, sensitive decisions, complex interpretation, or work that requires full institutional or historical context. In those cases, slower review and more robust tools are usually the better choice.
An example workflow
The following is one example of how someone might use browser-based AI. It is not a recommended or default practice.
Start with a public webpage you need to act on. Open Copilot in the Edge sidebar and try something like:
“Summarize this page in five bullets. Then list any dates, requirements, or next steps.”
From there, you might follow up with:
“Turn this into a short email update for a campus audience.”
“Create a one-paragraph brief I can paste into my notes.”
The key is to treat Copilot as a helper for that specific page, not as a general research tool. You remain responsible for reviewing summaries and extracted details against the original source before using or sharing them.
Choosing the right tool for Iowa work
Browser-based AI can be useful for public information and early sense-making. It is optional and situational, not a preferred starting point. When work moves into internal context, drafts meant for distribution, sensitive data, or ongoing collaboration, University-supported AI tools are the better fit.
Microsoft Copilot Chat is one such University-supported tool, designed for everyday workplace use with enterprise protections in place. Other University-supported AI tools are also available, and some may come with additional access requirements or costs.
The AI Tools page outlines which tools are appropriate for different kinds of work and data. In practice, browser-based AI can shorten the step between reading something and deciding what to do with it. The judgment, review, and responsibility still stay with the person doing the work. Subscribe to the AI at Iowa newsletter for more campus-focused updates and practical guidance.