> For the complete documentation index, see [llms.txt](https://docs.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.filed.com/reference/plugins/prowork/browser.md).

# Prowork for Chrome

Prowork for Chrome is an extension that connects your browser to Filed, so Prowork can complete work in the web tools you already sign in to. It is how Filed reaches practice management systems that have no API for the data you need — you stay signed in as yourself, and Filed works through your existing session.

## What the extension does

The extension gives Filed three abilities in your browser, and nothing more:

**Open and navigate browser tabs.** Filed opens the site it needs to work in, in a tab or a small window.

**Use approved website sessions.** When you connect an integration that relies on the browser, the extension reads that site's session so Filed can act as you. It only does this for the sites Filed is configured to work with.

**Run browser actions you requested in Filed.** Every action traces back to something you asked for — connecting an integration, or a task Prowork is completing for a client.

The extension has no access to sites outside that list, and does not browse on its own.

## Your credentials stay yours

Filed never sees your password or your verification codes. You sign in to each site directly, in that site's own page, exactly as you would normally. Filed uses the session that sign-in creates — the same thing that keeps you signed in when you close and reopen a tab.

## Before you start

* Google Chrome
* Access to the Filed workspace where Prowork will be connected

Each person installs the extension in their own browser. This is not a shared installation — every browser creates its own connection with its own login code. If you use more than one computer, you install and pair on each one.

{% hint style="info" %}
**Use the same Chrome profile you use for your practice management system.** The extension can only use sessions that live in the browser it is installed in. If you sign in to Canopy in one Chrome profile and install the extension in another, Filed will not find your session.
{% endhint %}

## Install the extension

{% stepper %}
{% step %}

### Add it from the Chrome Web Store

Search the Chrome Web Store for **Filed Prowork**, or use the link from the Prowork for Chrome page in Filed, and click **Add to Chrome**.

Chrome will list the permissions the extension asks for. These cover the sites Filed works in and the browser abilities described above.
{% endstep %}

{% step %}

### Pin it (optional)

Pin the extension to your toolbar so its side panel is one click away. You will need it in the next step.
{% endstep %}
{% endstepper %}

## Pair it with your workspace

The login code connects your browser to your Filed workspace. Filed shows it once, at the moment the connection is created, and it cannot be viewed again — the code acts as a credential for this specific installation.

{% stepper %}
{% step %}

### Start the connection in Filed

In Filed, go to **Plugins**, open **Prowork**, and choose **Prowork for Chrome**. Click **Set up Prowork for Chrome**.
{% endstep %}

{% step %}

### Name this browser

Give it a device name you will recognise later — most people use the computer it is installed on. Filed then generates your login code.

Keep this page open until you have finished the next step.
{% endstep %}

{% step %}

### Paste the code into the extension

Click **Copy code**, open the extension's side panel, and paste it where it asks for your login code.
{% endstep %}
{% endstepper %}

Your browser now appears under **Connections** on the Prowork for Chrome page, with an **Online** badge.

## Checking that it is working

The Prowork for Chrome page lists every browser paired to your workspace, who paired it, and when each was last seen.

**Online** means the extension has checked in within the last few minutes. It checks in every thirty seconds while Chrome is running.

**Offline** means Filed has not heard from it recently. That is normal when Chrome is closed. If Chrome is open and it still reads Offline, confirm the extension is enabled at `chrome://extensions`, then reload the Filed page.

## Keeping it up to date

Chrome updates the extension automatically from the Chrome Web Store. The version each browser is running is listed next to it on the Prowork for Chrome page, which is worth checking if something is behaving unexpectedly.

## Removing a browser

Removing the extension in Chrome stops it immediately. To tidy up the entry in Filed, open the browser's row on the Prowork for Chrome page and disconnect it there. Any integration that relied on that browser will need a different one, or the same browser paired again.

## What to do about a warning in Chrome

Newly published extensions show a note saying they are "not trusted by Enhanced Safe Browsing" until they have been in the Chrome Web Store long enough to build a track record. It is expected for a recently published extension, does not affect installing or using it, and clears on its own.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.filed.com/reference/plugins/prowork/browser.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.