> For the complete documentation index, see [llms.txt](https://docs.surgecardano.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.surgecardano.com/tutorials/11.-managing-strategies-alerts-and-settings.md).

# 11. Managing strategies, alerts and settings

Pause, edit and archive your strategies, control how they sign, set up alerts, and share your results.

{% embed url="<https://drive.google.com/file/d/1GBtVKIzGi8MFK0wnWKEa5n7UgGSRHllR/preview>" %}

Once your strategies are live, this is how you stay in control. Pause everything with one press, choose what signs automatically, get alerts when something needs your attention, and share your results when a strategy finishes.

### What you'll learn

* The controls every strategy has
* Pausing all strategies at once
* Setting up transaction signing and Keep display awake
* Configuring notifications and email alerts
* Sharing a P\&L card
* Exporting wallets and using Hard Logout safely

### Strategy controls

| Control        | What it does                                               |
| -------------- | ---------------------------------------------------------- |
| Pause / Resume | Holds the strategy. Resume picks up where it left off.     |
| Stop           | Ends the strategy for good                                 |
| Clone          | Copies its settings into a new strategy                    |
| Edit config    | Changes limits while it runs                               |
| Archive        | Files a finished strategy away, with its full history kept |
| Kill strategy  | Shuts the strategy down immediately                        |

**Pause All:** if the market turns fast, press and hold **Pause All** in the header to freeze every strategy at once. Hold it again to resume them.

### Transaction signing

Strategies sign transactions from hot wallets in your browser tab. You choose how that works in **Settings → Transaction Signing**:

* **Automate signing off:** each background transaction waits for your approval, and shows its details first.
* **Automate signing on:** strategies sign without interrupting you.

Swaps and sends you make yourself always ask for approval, whichever setting you choose.

**Keep display awake** (Settings → Display) stops your screen from sleeping while the Surge tab is in front. Signing happens in your browser, so keep the tab open while strategies run.

### Notifications and alerts

* **The bell** shows fills, cycles, level triggers and system alerts.
* **Settings → Notifications** lets you add your email for critical alerts, such as strategy errors or stops, and choose which in-app and browser push alerts you get.

### Share your P\&L

Open a finished strategy from **Archived** and click **Share P\&L**.

* Three card formats: Default, Square and Story
* Your wallet address is never shown, and showing the strategy name is optional
* Download the card, copy it, or post it straight to X

### Data and security

In **Settings**, you'll also find:

* **Data Management:** export and import your wallets, and Hard Logout, which clears everything from this browser
* **Wallet Security:** the security terms you accepted

### Good to know

* **Export your wallets before you use Hard Logout.** It removes everything from this browser, including your hot wallet keys.
* **Automate signing only on a device you trust.** With it on, strategies sign without asking.
* **Add your email for critical alerts,** so you hear about a stopped strategy even when the tab isn't in front of you.

### Next

[12. SURGE staking and fee tiers](/tutorials/12.-surge-staking-and-fee-tiers.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 by asking a question.

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

```
GET https://docs.surgecardano.com/tutorials/11.-managing-strategies-alerts-and-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.