# UpScalp Learning Path

**Last reviewed:** 2026-05-22.

Use this page when you do not know which guide to read next. Choose the path that matches the problem you are solving now.

## Choose by outcome

| Outcome                         | Read first                                                                                                                                            | Then read                                                                                                                |
| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| Start safely from zero.         | [Get Started Guide](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-get-started)                                                           | [Telegram Setup](https://upscalp.gitbook.io/upscalp-docs/setup/upscalp-telegram-setup)                                   |
| Understand the next signal.     | [How to Read Signals](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-how-to-read-signals)                                                 | [Risk Management](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-risk-and-safety)                            |
| Stop taking weak trades.        | [When to Skip a Signal](https://upscalp.gitbook.io/upscalp-docs/trading-principles/upscalp-when-to-skip-a-signal)                                     | [Why Context Matters](https://upscalp.gitbook.io/upscalp-docs/trading-principles/upscalp-why-context-matters)            |
| Fix missing messages.           | [Signals Not Arriving](https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-troubleshooting-no-signals)                                    | [Status and Service Updates](https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-status-and-service-updates) |
| Check approved beta boundaries. | [What UpScalp Does and Does Not Automate](https://upscalp.gitbook.io/upscalp-docs/trading-principles/upscalp-what-upscalp-does-and-does-not-automate) | [Premium Verification](https://upscalp.gitbook.io/upscalp-docs/setup/upscalp-premium-verification)                       |

## If you are new

Read these in order:

1. [Get Started Guide](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-get-started)
2. [Lite vs Premium](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-plans-and-access)
3. [Telegram Setup](https://upscalp.gitbook.io/upscalp-docs/setup/upscalp-telegram-setup)
4. [How to Read Signals](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-how-to-read-signals)
5. [Risk Management](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-risk-and-safety)

Do not start with trade-management pages until you can read entry, stop loss, take-profit levels, and context without guessing.

## If you receive signals but trade poorly

Read these:

1. [When to Skip a Signal](https://upscalp.gitbook.io/upscalp-docs/trading-principles/upscalp-when-to-skip-a-signal)
2. [How UpScalp Helps You Avoid Bad Trades](https://upscalp.gitbook.io/upscalp-docs/trading-principles/upscalp-avoid-bad-trades)
3. [Why Context Matters](https://upscalp.gitbook.io/upscalp-docs/trading-principles/upscalp-why-context-matters)
4. [Trading Principles](https://upscalp.gitbook.io/upscalp-docs/trading-principles/upscalp-trading-principles)

This path is for discipline, not setup.

## If your issue is after entry

Read these:

1. [Partial Profit and Breakeven](https://upscalp.gitbook.io/upscalp-docs/trading-principles/upscalp-partial-profit-and-breakeven)
2. [Risk Management](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-risk-and-safety)
3. [What UpScalp Does and Does Not Automate](https://upscalp.gitbook.io/upscalp-docs/trading-principles/upscalp-what-upscalp-does-and-does-not-automate)

Check automation boundaries before assuming any product path manages positions for you.

## If something is broken

Use these instead of rereading trading guides:

1. [Signals Not Arriving](https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-troubleshooting-no-signals)
2. [Status and Service Updates](https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-status-and-service-updates)
3. [Contact Support](https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-contact-support)

## If you are checking Private Beta

Start here:

1. [Lite vs Premium](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-plans-and-access)
2. [What UpScalp Does and Does Not Automate](https://upscalp.gitbook.io/upscalp-docs/trading-principles/upscalp-what-upscalp-does-and-does-not-automate)
3. [Premium Verification](https://upscalp.gitbook.io/upscalp-docs/setup/upscalp-premium-verification)

Private Beta API access is controlled and approval-based. Do not treat it as a public self-serve path. Do not create exchange API keys unless an approved beta setup flow explicitly tells you to do so, and never enable withdrawal permissions for any exchange connection.

## When to stop reading and act

Move from reading to setup only when the current guide gives a clear next action. If the next action depends on a missing access state, unclear Telegram route, unverified link, or unsupported API assumption, use the troubleshooting or official-link guide before continuing.

## Related

1. [Get Started Guide](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-get-started)
2. [How to Read Signals](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-how-to-read-signals)
3. [Risk Management](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-risk-and-safety)
4. [Official Links and Channels](https://upscalp.gitbook.io/upscalp-docs/reference/upscalp-official-links)


---

# Agent Instructions: 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:

```
GET https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-learning-path.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
