> For the complete documentation index, see [llms.txt](https://copilot-docs.bugbase.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://copilot-docs.bugbase.ai/enterprise/how-to-trigger-an-external-scan/importing-browser-session.md).

# Importing Browser Session

Use **Import Existing Session** when you already have a browser session JSON bundle from another target, workspace, or previous export.

### Import from JSON

1. Open the target domain settings drawer.
2. Click **Record Browser Session** to open **Browser Session Manager**.
3. In the session selector, choose **Import an existing session**, or switch the mode selector to **Import Existing Session**.
4. Paste the browser session JSON or upload the JSON file.
5. Review or edit the session context, tags, browser actions, and authentication verification regex.
6. Select the email identity for this session, or choose **None** when the imported session uses a customer-managed account or long-lived login.
7. Save the imported session.

The imported session appears in the browser-session dropdown for that target. Validate it before using it for authenticated scans.

{% content-ref url="/pages/qlsZUTSSIvcyvgbeitK1" %}
[Validating Browser Sessions](/enterprise/how-to-trigger-an-external-scan/validating-browser-sessions.md)
{% endcontent-ref %}

### What the JSON Contains

A browser session JSON bundle can include:

* recorded browser actions;
* cookies and storage;
* authentication verification URL and regex;
* valid-session page hashes;
* WebAuthn credentials;
* email identity metadata;
* session context and tags.

### Legacy Extension Exports

Older browser-session extension exports can still be imported if you have the JSON output. You do not need to install the old Chrome extension to import a session into the current product flow.