> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gumloop.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Why is the browser turned off for me?
The agent browser is off for one of two reasons: the **Browser** section on the agent was never turned on and saved, or your organization role doesn't include the **Agent browser** feature. If the **Browser** section says **Turned off for your role**, only an organization admin can fix it.
## What do I see, and what do I do?
Check the **Browser** section on the agent's **Agent** tab.
| What you see | Why | What to do |
| - | - | - |
| **Give your agent a browser** with a **Turn on** button | The browser is off on this agent | [Turn it on and save](#how-do-i-turn-on-the-browser-for-an-agent) |
| **Turn on** is greyed out | You can view the agent but not edit it | Ask an owner of the agent to turn it on, or to give you edit access. See [Let someone edit your agent](/help/sharing/let-someone-edit-an-agent) |
| **Turned off for your role**, with **Request access** | Your role doesn't include **Agent browser** | [Request access from an admin](#turned-off-for-your-role) |
## How do I turn on the browser for an agent?
1. Open the agent and go to the **Agent** tab.
2. In the **Browser** section, click **Turn on**.
3. Click **Save**. The browser works from your next message.
New custom agents have the browser on by default when their creator is allowed to use it. Older agents start with it off. [Gumball](/core-concepts/gumball) needs no setup.
What do I do when it says "Turned off for your role"?
Your organization hasn't given your role the **Agent browser** feature, so agents you run work without the browser.
1. In the **Browser** section, click **Request access**.
2. Pick an administrator, add a short note, and send the request.
If no administrator is listed, contact one of your [organization admins](https://www.gumloop.com/settings/organization/members?role=admin) directly and ask them to add **Agent browser** to your role. You don't need to change the agent afterwards.
## How does an admin turn on Agent browser for a role?
On Enterprise organizations, **Agent browser** is off by default in [Custom roles](/enterprise-features/user_groups).
1. Go to **Settings** > **Organization** > **Custom Roles**.
2. Click the person's role. To turn it on for everyone, open your default role.
3. Open the **Features** tab, click **Add Features**, select **Agent browser**, and click **Add Features**.
The change applies from the person's next message. No one needs to rebuild their agents.
## Why does the browser work for me but not my teammate?
Browser access is checked for the person who **runs** the agent, not the person who set it up. A teammate whose role lacks **Agent browser** gets the agent without the browser, even though it's turned on. An admin needs to add **Agent browser** to their role.
## The browser is on, but the agent doesn't use it. Why?
The agent may pick a faster tool, such as a connector, when one covers the app. To force the browser, ask for it by name, for example: *"Use your browser to open example.com and download the latest invoice."* See [Which should my agent use: connector, API, or browser?](/help/browser/browser-vs-connector-vs-api).
## Related
What the browser can do, handoffs, limits, and billing
Grant or restrict Agent browser per role