> For the complete documentation index, see [llms.txt](https://securitybot.gitbook.io/securitybot-knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://securitybot.gitbook.io/securitybot-knowledge-hub/bot-guide/administering-securitybot/changing-settings.md).

# Changing Settings

SecurityBot offers flexible configuration options, all controlled through slash commands directly within Discord. These settings allow you to fine-tune how SecurityBot operates in your community, from filters and roles to verification and purge behaviour.

Only users with the **Admin role** or **Discord’s Administrator permission** can modify settings.

***

### View Your Current Configuration

```
/settings view
```

Displays a private summary of your current setup, including:

* Log channel
* Admin and mod role
* Filter status and settings
* Chat alerts
* And more!

Use this command to quickly verify your bot’s core configuration.

***

Each filter and list has its own `view` subcommand. For example:

```
/chat_filters address view
/chat_filters domain view
/user_filters nickname view
/user_filters avatar view
/chat_filters exempt_channel view
```

These let you view allowed addresses, domains, handles, invites, blocked nicknames, protected avatars, exempt channels, and exempt categories.

***

### Best Practices

* Assign admin privileges only to trusted teammates
* Keep logs visible only to necessary users
* Regularly review allowlists using the relevant `view` subcommands
* Use `/settings view` to confirm SecurityBot's core settings

***

Next up: Get answers to common questions in the [FAQ](/securitybot-knowledge-hub/faq/frequently-asked-questions.md).


---

# 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://securitybot.gitbook.io/securitybot-knowledge-hub/bot-guide/administering-securitybot/changing-settings.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.