Skip to content
NUKBORD / PRODUCT MANUAL12 practical guides

A clear way into the workstation

Know your tools.
Make them yours.

Start with an account, build your workspace, prepare deliberately and keep the record. Follow practical instructions for the controls in front of you.

1 of 12 practical guidesClear manual filters โ†’
01Choose a job02Follow the steps03Find account help
Published manual introduction

The guides below are the product manual. An optional published introduction can add context; it does not replace the search, instructions or account help.

01 / Find your next task

Choose a job.

Each guide includes preparation, ordered steps, checks and the limits that matter.

02 / Order safety

Handle unknown outcomes and protection limits

Understand the workstationโ€™s boundaries before executing an order or enabling protection. Checking an uncertain result is different from dispatching another request.

01

Keep the original request

  1. Stop when the outcome is unknown

    If the workstation cannot tell whether a request reached the broker, it retains the original request. An unknown result is not evidence that nothing happened.

  2. Check instead of blindly resending

    Read the unresolved action feedback and available execution review. The recovery path checks the original outcome, including after a restart; it does not blindly send the order again.

  3. Inspect actual evidence

    A local observation, broker-confirmed fill and missing field are different facts. Keep unavailable amounts and comparisons unavailable rather than treating them as zero.

Check your work

An unresolved original remains identifiable and has not been mistaken for a fresh request.

02

Know the execution boundaries

  1. Research cannot dispatch

    Browsing, editing lists, drawing and staging cannot send an order on their own. Screens, backtests and paper simulations never send real orders.

  2. Review protection before enabling it

    The app only acts on protection rules you reviewed and switched on. Trailing stops, stop-to-entry and partial targets depend on the open, signed-in, connected app.

  3. Plan for a stopped app

    When the app closes, only stop-loss and take-profit actually held by the broker remain. A local running rule is not a promise of continued protection after sign-out or disconnection.

Check your work

You know what requires explicit execution review and what stops with the app.

03 / Keep the definition handy

Workstation reference.

1 of 10 public references. The capability descriptions remain separate from the step-by-step guides.

Order safetySafety rules

The workstation never blindly resends an order whose outcome is unknown, and orders are sent only by you or by protection rules you reviewed and switched on.

  • An order whose result is unknown is checked, not blindly sent again, including after a restart
  • Screens, backtests and paper simulation never send orders
  • Browsing, list editing and staging cannot send an order on their own
  • Protection rules run only while the app is open, signed in and connected
  • Facts, derived readings and unavailable data are labelled differently

Connections drop and applications restart. When the workstation cannot tell whether an order reached your broker, it keeps the original request and checks what happened instead of sending the order again.

Apart from orders you send yourself, the only orders the app sends come from protection you reviewed and switched on: trailing stops, stop-to-entry and partial targets. Those run only while the app is open, signed in and connected, and pause when you sign out, change account or lose the connection. When the app is closed, only the stop-loss and take-profit held by your broker remain.

Throughout the app, values that come straight from your broker or data source, values the app calculated, and values that are simply not available are shown differently, so you always know which is which.

Read the Order safety guide