# Browser permissions and safety

Review domain, account, scope, and proposed action before approval; keep purchases, publishing, messaging, and deletion manually gated.

![Browser permissions and safety in Foxora Desktop v5.0.3](/docs/images/v5.0.3/desktop/stage-browser.webp)

## Where this lives

Open a task, then choose **Stage → Browser**.

Foxora can operate an isolated managed browser or an authorized existing browser context, while showing navigation, screenshots, actions, and takeover state on the Stage.

> **Safety:** Browser actions can create irreversible external changes. Never expose more browser state or account access than the task requires.

## Steps

1. Open a task, then choose **Stage → Browser**.
2. Review domain, account, scope, and proposed action before approval.
3. Keep purchases, publishing, messaging, and deletion manually gated.
4. **Confirm the result.** Inspect the final URL and page state, then independently confirm any submitted, published, purchased, or deleted result.

## Choose the right path

- Use managed mode for isolated research and testing.
- Use an existing signed-in context only when account state is necessary.
- Take over for authentication, captchas, or sensitive confirmation.


## Confirm it worked

- Inspect the final URL and page state, then independently confirm any submitted, published, purchased, or deleted result.
- The screen, command, file, run, or destination named in this guide reflects the expected state.