> 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.


---

# 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://copilot-docs.bugbase.ai/enterprise/how-to-trigger-an-external-scan/importing-browser-session.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.