Claude in Chrome: browser tasks a team can delegate, and when to integrate instead

Claude in Chrome: browser tasks a team can delegate are the ones that are repetitive, visible on screen and easy to check. Good examples are filling web forms, gathering facts across several tabs and working through admin portals that have no integration. Work that writes to your CRM, helpdesk or accounting system every day is better served by a proper integration.

Claude in Chrome is Anthropic's browser extension that lets Claude read pages, click, type, fill forms and move between tabs using the logins you already have. In practice it does the clicking that a person would otherwise do, on the same screens.

This guide is written for the office manager who has to decide what goes to the extension and what stays with people. It covers:

• what the extension does and which plans include it
• which tasks suit it, with a worked example
• what must stay with a person
• the safety settings to decide before anyone starts
• when an integration beats the browser

If you want the admin console walkthrough and plan details in more depth, read our earlier post on Claude in Chrome plans, admin and safe use. This post focuses on the tasks themselves.

Claude in Chrome reads the page you are signed in to, then clicks, types and fills forms while you decide what happens next. Anthropic's Claude in Chrome page says it can reach internal tools, legacy portals, admin consoles and invoice systems. It works with the logins you have, on the tab in front of you. Anthropic lists three ways to use the extension:

• The side panel, when the work is on the page in front of you and nothing else needs to be open.
• Claude Cowork, when the browser is one step in a longer job.
• Claude Code, for developers who want Claude to check its work in a real browser.

Cowork is Claude's desktop mode for knowledge work beyond coding. It runs locally in an isolated virtual machine with access to local files and MCP integrations. The side panel now runs a full Cowork session. Any skills, plugins and connectors your team has already built are there, with nothing to set up in the browser. A skill is a way to teach Claude a repeatable workflow. A connector is a link from Claude to another program. Our page on how Claude Cowork works for UK firms explains the desktop side. Two further details matter for a team. Sessions live with the user's account, not the machine, so someone can start a task in Chrome and finish it on desktop or mobile. Cowork also has its own built-in browser, fully separate from personal browsing. It is the default unless the user already uses Claude in Chrome.

Claude in Chrome is available on every paid Claude plan: Pro, Max, Team and Enterprise. A setup guide from claude/for reports that Anthropic announced general availability on every paid plan on 26 August 2026. The same guide notes that the help centre still called the side panel beta when it checked on 6 October 2026. The plans differ in price and in admin control. Prices below come from Anthropic's pricing page and are in US dollars.

Plan	Price	Org-wide extension switch and site lists
Pro	$17 per month billed annually, $20 billed monthly	Not listed
Max	From $100 per month	Not listed
Team (2 to 150 people)	Standard seat $20 per seat per month billed annually, $25 billed monthly	Yes
Enterprise	US$20 per seat per month billed annually, 20 seat minimum, plus usage at API rates	Yes

For a business, the admin column decides it. Only Team and Enterprise let an administrator switch the extension on or off for the whole organisation and set site allowlists and blocklists. On Max and Team, the side panel already runs as a Cowork session, and this is rolling out to Pro. Two practical limits apply. Every plan has usage limits that reset on a rolling five-hour window, and paid plans add weekly limits on top. The extension is not supported on other Chromium browsers, so staff on Edge or Brave need Chrome for this work. For seat costs across a whole year, see our guide to what Claude for business costs and how to start.

The browser tasks that suit Claude in Chrome share four traits. They repeat, they happen on a site you are already signed in to, the result is visible on screen, and a mistake can be corrected. Three groups of office work fit that pattern well.

Web forms

Entering the same details into a supplier registration form, a carrier booking page or a trade body's renewal form is slow and error-prone by hand. Claude in Chrome reads the source information on one tab and types it into the form on another. You review the filled form before it is sent.

Research across tabs

Comparing delivery terms on three supplier sites, or collecting opening hours and contact names from a list of venues, means a lot of tab switching. The extension can move between tabs, note what it finds and give you a summary you can check line by line.

Admin portals without an integration

Many firms rely on a legacy supplier portal, a landlord's maintenance system or a government-style admin console that offers no API. Anthropic names legacy portals, admin consoles and invoice systems as places the extension can work. For a portal like this, a browser is often the only practical way in.

What these groups have in common is low stakes per action and a person close by. A wrong field in a draft form costs a minute to fix. A wrong entry posted to your accounts costs far more, which is why that kind of task appears later in this guide under integrations.

The worked example below shows one realistic delegation from start to finish. An office manager spends every Monday morning checking order status in a supplier's legacy portal. She copies each expected delivery date into the company's internal booking form, which is also a web page.

1. The admin allowlists two sites. On the Team plan, the administrator keeps the extension switched on and adds the supplier portal and the internal booking form to the site allowlist. Everything else stays blocked for now.
2. The user chooses Permissions Mode. In Permissions Mode she grants access one site at a time, starting with the portal.
3. She opens the side panel on the portal tab. She is already signed in, so Claude works with her existing login.
4. She gives a precise instruction. For example: "List every open order on this page with its expected delivery date. Then open the booking form tab and enter each date against the matching order number. Do not press Submit. Tell me when the form is ready to check."
5. She grants the second site when asked. Claude switches to the booking form, fills the fields and stops.
6. She checks and submits. She compares three or four rows against the portal, then submits the form herself.

Once the task runs cleanly, she saves the instruction as a skill so the same steps run the same way next Monday. Our guide to setting up Claude Projects and skills for a small team shows how to share that skill with colleagues.

Decisions that move money, delete data or reach a customer must stay with a person. Anthropic builds part of this in. Its Chrome page says purchases, financial actions and other one-way doors wait for you. The claude/for guide reports that purchases and permanent deletions are blocked outright. Anthropic also tells users to skip banking, health records and anything with credentials they would not share. Treat that as a firm boundary for your team, not a suggestion. Beyond those rules, keep these tasks with people:

• sending anything to a customer, supplier or regulator
• approving invoices, refunds or credit notes
• judgement calls, such as which supplier to choose or whether a complaint is justified
• changes to user accounts, permissions or passwords

The reason is not only caution. Anthropic states plainly that its protections are not foolproof and that Claude may hallucinate, leading to actions you did not intend. A prompt injection attack is one cause. It is an attempt by a malicious website or document to trick Claude into an unintended action, such as sharing bank details or deleting files. Anthropic's own safety article, as quoted in the claude/for guide, says the risk "is not zero". A person reviewing the result before it counts is the control that catches both errors and attacks.

Five safety settings for Claude in Chrome should be agreed before anyone on the team starts. Most take minutes to set and are hard to retrofit once habits form.

1. Organisation switch. On Team and Enterprise, decide whether the extension is on for everyone or only after training.
2. Allowlist and blocklist. List the sites Claude may use. Block banking, payroll and any site holding health or other sensitive personal data.
3. Permission mode per user. Permissions Mode grants access one site at a time. "Automatically approve" screens every action and uses more of the usage limit. "Skip all approvals" means nothing pauses and nothing checks Claude's actions, so reserve it for low-risk research, if you allow it at all.
4. Which login Claude uses. Claude acts with the user's own access. A user with admin rights in a portal gives Claude admin rights there too.
5. What is on screen. Claude takes screenshots of the tabs it works in, and whatever is visible becomes part of the conversation. Close unrelated tabs before starting.

At Svennis we start every Chrome rollout with Permissions Mode and a short allowlist of the portals the team already uses. We widen the list only after we have reviewed the first runs with the people who do the work. Write these choices into your staff guidance so a new starter gets the same settings as everyone else.

An integration beats Claude in Chrome when the task runs daily, writes to a system of record or needs to run without someone watching. Claude's tools differ mostly in how much of a task gets handed over, as one overview of Claude's ways of working puts it. The browser drives the same screens a person uses, one page at a time. An integration talks to the system directly, so it is faster, repeatable and easier to audit. The table below sorts common office tasks.

Task	Claude in Chrome	Integration
Fill a supplier's web form weekly	Good fit	Rarely worth building
Compare terms across three supplier sites	Good fit	Not needed
Check a legacy portal with no API	Good fit	Often not possible
Log every inbound request as a ticket in Zoho Desk	Slow, one screen at a time	Better build
Update deal stages in Zoho CRM after every call	Workable for a few records	Better build
Post supplier bills into Zoho Books	Financial actions wait for a person	Better build, with approval kept in the books

When Svennis connects Claude to a company's programs, we build one of four things for each connection: a connector, an MCP server, a plugin or a skill. We show the options with their cost, and the client chooses. Off-the-shelf plugins may already cover part of the need. Our post on which plugins a small team should start with lists the first ones to try.

For a UK company, Claude in Chrome raises three practical points: currency, data and ownership. None of them blocks adoption, but each needs a decision. First, Anthropic's pricing page lists prices in US dollars. Budget for exchange movements on annual Team or Enterprise seats. Refunds on these plans are set by Anthropic's Commercial Terms, not its consumer terms. The 14-day cooling-off right for consumers does not cover a business buying seats, so read the terms before you commit to a year. Second, data. On Team and Enterprise, Anthropic does not train its models on your content by default. That does not remove your own data protection duties. Claude in Chrome captures screenshots of the tabs it works in, so any customer or employee details visible on screen become part of the conversation. Check which portals on your allowlist show personal data. Keep health records and banking off it entirely, as Anthropic advises. Third, ownership. Someone in the business must own the allowlist, the permission mode policy and the review of what Claude did. In a small firm that is usually the office manager or operations lead. Give that person the admin role on the Team plan and a short monthly check of which sites are allowed and why.

The next steps below take you from a list of chores to a safe first run.

1. List the browser chores. Ask each person to note the web tasks they repeat each week and how long each takes.
2. Sort them with the table above. Mark each as Claude in Chrome, integration, or stays with a person.
3. Confirm the plan. If several people will use the extension, a Team plan gives you the org-wide switch and site lists.
4. Set the five safety settings. Start with Permissions Mode and a short allowlist.
5. Run one task the way the worked example does. Keep the final submit with a person, then save the steps as a skill.
6. Collect the integration candidates. Tasks that touch your CRM, helpdesk or accounts every day belong in a proper build.

When you are ready to go further, Svennis works in four steps. A Workshop maps your processes. Then comes a pilot: Pilot Claude A puts an AI agent on Claude to work on one process, or Pilot Claude B sets up Claude Team for the whole team. A department Activation follows, then monthly operations. If browser work across a team is your starting point, read how Pilot B sets up Claude Team in 30 days.