> For the complete documentation index, see [llms.txt](https://docs.sigma.win/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sigma.win/setup-trading-and-management/sol/management/settings.md).

# Settings

Interactive Guide

{% embed url="<https://app.guideflow.com/player/ok8l1l2ixr>" %}

### Within the Settings menu, you can customize:

{% stepper %}
{% step %}

### Default Trading Values

**Sell Fee:** Your default gas on sell txs

**Price Impact:** The maximum token price % change because of your tx that you're willing to accept

**Min Liquidity:** The minimum amount of pooled SOL in the token's liquidity pool required for your tx to execute&#x20;

**AntiMev / AntiMev Tips:** When you use high slippage, your tx becomes susceptible to sandwich attacks. MEV protection on Sigma shields you from this by routing your txs through private relays, but may make your tx slower. Adding an anti-MEV tip prioritizes your tx being processed when MEV protection is on.
{% endstep %}

{% step %}

### Enable/Disable Trade Confirmation Messages

{% endstep %}

{% step %}

### Default Gas Buttons

{% endstep %}

{% step %}

### Default Buy Buttons

{% endstep %}

{% step %}

### Enable and Configure Auto Buy

{% endstep %}

{% step %}

### Whether to Auto-Generate PnL Cards

{% endstep %}

{% step %}

### Menu Language

{% endstep %}
{% endstepper %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sigma.win/setup-trading-and-management/sol/management/settings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.