> For the complete documentation index, see [llms.txt](https://docs.symm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.symm.io/trader-documentation/how-trading-works-in-symmio/using-take-profit-and-stop-loss.md).

# Using Take Profit and Stop Loss

Take profit (TP) and stop loss (SL) let you exit a position automatically when the market reaches a price you picked in advance: a profit target on one side, a maximum acceptable loss on the other. You set the levels once instead of watching the chart all day, and the system closes the position for you when a level is hit.

On Symmio, every position is an on-chain agreement between you and a specific solver, so TP/SL lives outside the position itself: a small service watches the market on your behalf and submits a close request the moment your trigger is reached. Under the hood that service works one of two ways: either you delegate permission to a service allowed to request closes for you when price conditions are met, or the frontend talks directly to a solver's Conditional Orders API and the solver manages TP/SL. From your side the result is identical: when price hits your TP or SL, a close request goes out.

### How it works for you as a trader

The exact UI differs between frontends, but the flow is usually the same.

**Open a position.** Trade as usual, then go to the "Positions" or "Open Positions" tab.

**Find the TP/SL controls.** Next to your position you'll see a TP/SL button or a settings icon. Click it to open the take-profit / stop-loss panel.

<figure><img src="/files/fGAAO4EPlBbpxwWqNIwR" alt=""><figcaption><p>Setting a TP/SL on Carbon</p></figcaption></figure>

**Approve the control.** The first time you set TP/SL, you'll usually be asked to approve either conditional order functionality or instant trading; both enable conditional order management. This approval is what lets the frontend or solver request a close for you when your conditions are met.

{% hint style="info" %}
You stay in control of your funds. The service cannot withdraw or move your money; it can only send the same close requests you could send yourself.
{% endhint %}

**Choose your levels.** Set a take profit (where you're happy to lock in gains) and a stop loss (where you want to cut the trade to cap downside). Most frontend builders let you use percentages or enter exact prices if you already know your target and invalidation levels.

<figure><img src="/files/6yeY6wDdD9Otsy2qPIPt" alt=""><figcaption><p>Setting a TP/SL on Carbon</p></figcaption></figure>

Behind the scenes, the app turns your choices into a conditional order payload that includes the trigger price (where TP/SL activates) and a minimum acceptable execution price (which builds in slippage protection).

**Confirm and save.** Once you confirm, the system watches the market and attempts to close your trade whenever a threshold is reached, for as long as the position stays open and your conditions are valid.

**Adjust or remove later.** Come back to the same panel any time to move your take profit, tighten or loosen your stop loss, or cancel TP/SL entirely.

{% hint style="info" %}
Check your specific frontend's documentation for any differences.
{% endhint %}

### What you're authorizing

The delegation is deliberately minimal, and it's worth knowing exactly what it does and doesn't allow.

The service can submit `requestToClosePosition` on positions in your account, for as long as the delegation is active. That's the whole of it. It cannot:

* open new positions or modify existing ones,
* withdraw, deposit, allocate, or deallocate collateral,
* change your account settings or delegate further permissions,
* call any other function on the Symmio contracts.

The delegation carries an expiry timestamp (typically a day, or a session length, depending on the frontend) and can be revoked early if you want permission back before it lapses. Revocation runs through a short two-step cooldown so an in-flight trigger can't be cut off mid-execution.

### What happens when your trigger fires

When the service's price feed crosses your TP or SL level, it submits the close as a market order against your solver. A few consequences follow from that:

* Your solver (PartyB) fills the close, exactly as it would any other market close request.
* You pay a close fee on the filled position, deducted from your available balance as part of the solvency check that runs when the solver fills. Close fees are set by the affiliate your frontend is registered under, so different frontends may charge different rates on the same symbol.
* The price you get is your solver's fill price, not the exact level that triggered the close. In fast markets, expect some slippage between trigger and fill, especially on a stop loss during a sudden move against you.


---

# 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.symm.io/trader-documentation/how-trading-works-in-symmio/using-take-profit-and-stop-loss.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.
