---
title: "How to bypass the local access permission dialog"
slug: "bypass-local-access-dialog"
updated: 2026-06-23T06:16:39Z
published: 2026-06-23T06:16:39Z
canonical: "helpcenter.autify.com/bypass-local-access-dialog"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://helpcenter.autify.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to bypass the local access permission dialog

This article explains the steps to bypass the "local access permission" dialog displayed by the browser when running a test that accesses an API in a local environment using Autify Nexus.

Due to the specifications of Autify Nexus, it is not possible to automatically operate the allow button on the browser's confirmation dialog, so configuration using this procedure is required.

![](https://cdn.document360.io/c040854c-2c75-49d0-98e1-43f462e8657e/Images/Documentation/local access permission-en.png?sv=2026-02-06&spr=https&st=2026-10-27T18%3A40%3A04Z&se=2026-10-27T19%3A40%3A04Z&sr=c&sp=r&sig=Fdng9FpBCNqhxuhVFCQHra3MDBinEeZY5NkQtRgGH9A%3D)

## Prerequisites

- The local API to be tested is running.
- The browser used is Chromium-based (Chrome or Microsoft Edge).

## Types of bypass methods

There are two approaches to bypass the dialog. Please choose according to your use case and operation.

- **Method 1: Configure in the Advanced options of the Test Plan (Global setting):** Suitable when you want to apply it at once to all scenarios included in a Test Plan.
- **Method 2: Use a Playwright code step (Per-scenario setting):** Suitable when you want to grant permissions individually to a specific scenario only, or at a specific timing.

## Method 1: Set a JSON string in the Advanced options of the Test Plan

### Steps

1. Open the details screen of the target test plan.
2. Click **Advanced options** in the **Test plan settings** section to expand it.
3. Click **Configure with JSON** and enter the following JSON string:

```json
{  
  "launchOptions": {  
    "args": [  
      "--disable-features=BlockInsecurePrivateNetworkRequests",  
      "--disable-web-security",  
      "--allow-insecure-localhost"  
    ]  
  }  
}  
```

If a JSON string has already been entered, add the above three arguments to `launchOptions.args` while keeping the existing settings.

4. Click **Done** at the bottom of the dialog.

5. Click **Save** in the upper right corner of the screen.

6. After saving the settings, run the test plan and confirm that it proceeds without displaying the dialog.

### Notes

- Because this setting relaxes the browser's security features, use it only in a test environment.

## Method 2: Use a Playwright code step (Per-scenario setting)

This method directly adds a step to a specific scenario to grant access permissions to the local network.

### Procedure

1. Click the target scenario from the scenario list to open it.
2. Click **Add** at the top of the step list (right before the 1st step).
3. Select **Insert step** from the displayed menu.
4. Click **Playwright code step**.
5. Paste the following code into the **Code** field in the insert dialog:

```typescript
await context.grantPermissions(['local-network-access']);
```
6. Click **Insert** to add the step.
7. Click **Save** at the top of the screen.
8. Click **Run now** at the top of the screen and confirm that the test proceeds without the dialog appearing.

### Notes

- Can only be executed with a Playwright code step: Be sure to perform this procedure using a "Playwright code step". It cannot be substituted with a JavaScript step.
- Placement of the step: The added step must be placed as the "1st step" of the scenario (place it before existing steps such as page transitions).