# Error: This page cannot be scripted due to an ExtensionsSettings policy

If you landed on this page is that you must probably face the following error: 

<mark style="color:$warning;">This page cannot be scripted due to an ExtensionsSettings policy.</mark>

It means that your browser or organization’s admin policy is preventing the Birdie Chrome extension from running on certain pages — usually internal or enterprise-managed ones.

### Why this happens

Birdie’s Chrome extension needs permission to inject a small script into your web page to display the toolbar and start recording.\
Some companies’ Chrome configurations or enterprise policies block extensions from injecting scripts on specific domains such as `*.app.acme.com` or `*.acme.com`

***

### How to fix it

#### 1. If you have admin access in Chrome

1. Open a new tab and go to `chrome://policy`
2. Search for `ExtensionSettings` or any URL-blocking policy that might include:
   * the Birdie extension ID, or
   * your company domain (for example, `*.acme.com`)
3. Update the settings to **allow Birdie to run scripts** on your domain.
4. Reload the page and try again.

***

#### 2. If your Chrome browser is managed by IT

If you see the message **“Your browser is managed by your organization”** in Chrome settings, you’ll need help from your IT team.

Ask your IT administrator to whitelist Birdie for your company’s internal domains.

They can do this by adding (or updating) the following configuration in their Chrome policy management console:

```json
{
  "ExtensionSettings": {
    "*": {
      "installation_mode": "allowed"
    },
    "glkfmfjeafnooojgeobbhdjhdejocoap": {
      "runtime_blocked_hosts": []
    }
  }
}
```

In addition, make sure your company’s internal URLs (like `*.app.acme.com` and `*.acme.com`) are **not** included in any blocked host patterns.

> 🔒 **Note:**\
> The `glkfmfjeafnooojgeobbhdjhdejocoap` value above is Birdie’s official Chrome Extension ID.\
> You don’t need to replace it — just copy it as is.

### Once the policy is updated

After your IT team updates the policy:

* Relaunch Chrome (or restart your computer)
* Reopen the page and try recording again

Birdie should now be able to attach its toolbar and start recording as expected.


---

# Agent Instructions: 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:

```
GET https://docs.birdie.so/birdie-docs/troubleshooting/extension/error-this-page-cannot-be-scripted-due-to-an-extensionssettings-policy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.