> For the complete documentation index, see [llms.txt](https://docs.venn.build/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.venn.build/venn-network/getting-started/protocols-and-developers/roles.md).

# Roles

## Firewall Admin

The `FIREWALL_ADMIN` is the wallet or account that can configure your firewall's settings. Such as which `Firewall` instance your smart contracts use, what security policies are enabled, and whether the policies are enabled globally or on specific methods.

### Default Configuration

By default, when you [integrate the Firewall SDK](https://docs.venn.build/venn-network/getting-started/protocols-and-developers/installation#step-1-integrate-the-firewall-sdk) into your smart contracts `FIREWALL_ADMIN` role is set as `msg.sender`- which means it's the same as the wallet or account that was used to deploy your smart contracts.

### Changing The Default Configuration

After your smart contracts have been deployed, the `FIREWALL_ADMIN` can call the `setFirewallAdmin(...)`followed by a call to `acceptFirewallAdmin()`to set a new Firewall Admin on your smart contract:

```
setFirewallAdmin(address _newFirewallAdmin)
```

```
acceptFirewallAdmin()
```

{% hint style="warning" %}
The Firewall Admin must be set per each smart contract using the Venn Firewall
{% endhint %}


---

# 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://docs.venn.build/venn-network/getting-started/protocols-and-developers/roles.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.