Workspace, strategies and account

Sign in and return to your work

Open Screebits and use an available sign-in method. Google and email-link sign-in can have different availability. If the sign-in screen identifies an existing provider, use that method rather than creating a second identity. Follow any required account setup before entering the dashboard. Never share a sign-in link or verification code.

If your session expires while editing, sign in again and verify the saved strategy before continuing. See saving and conflicts for changes that were not confirmed saved.

Organize strategies

Open Strategies. Search by name and combine mode, deployment, tag and sorting controls. Clear filters when the list is unexpectedly empty; use pagination to see more results.

• Open the strategy name for Details: inspect mode, saved graph summary, versions and Backtest history.
• Choose Edit in editor to change the current graph.
• Use Strategy actions to edit its name, description or tags. These describe the strategy; its mode remains permanent.
• Duplicate creates a separate strategy from the current saved snapshot, description and tags. It uses another strategy slot. Give the copy a distinctive name before experimenting.
• Delete strategy removes the strategy and its saved versions from the active workspace after confirmation. Historical Backtests remain separate. A checkpoint within the deleted strategy is not an independent backup.

An Active strategy status means it is present in your workspace. Read deployment separately; do not interpret Active or Saved as proof that a strategy is trading live.

Preserve versions

Use Save strategy for current changes and Save checkpoint for a named point you want to find again. In Version history, distinguish the current Main version from historical previews. Restoring a version changes the current strategy through a recorded restoration; previewing alone does not.

Version retention depends on plan and category. Do not assume every autosave is permanent. Read checkpoints and restore before replacing current work.

Change language and theme

Open the user menu at the bottom of the sidebar. Choose Language for English or Italian and the theme control for appearance. Settings → Profile also exposes profile and appearance options. Workspace language and documentation language are separate controls; product help opens the corresponding documentation language.

In the editor, Preferences controls canvas appearance locally. Preferences → Settings changes strategy settings after applying and saving them. Neither is the Backtest’s execution-cost configuration.

Read plan and usage

Open Settings from the user menu. Use Subscription for current plan, billing status, payment method and available billing-management actions. Use Usage for resource counts, limits and reset information. If a summary is stale or unavailable, refresh it before relying on the displayed remaining capacity.

Plan, role and feature capability are distinct. Free, Pro and Elite are plans. Special account roles may have different access, so another user’s screenshot is not a guarantee for your account. Exact prices, quotas and retention are shown by the current product, not fixed by these guides.

Manage billing deliberately

From Subscription, use the offered upgrade or billing-management action. Review the selected plan, interval, price and renewal information before confirming with the payment provider. Returning from checkout is followed by a verification step; wait for confirmed subscription status. Canceling a checkout does not by itself complete a subscription change.

For a payment problem such as past due, use the existing subscription’s recovery or billing-management action instead of trying to create a second subscription. Invoice history and downloads are available through the billing surface where offered. A data-load failure is not proof that no subscription exists.

Account and security actions

Settings separates Profile, Account and Security. Profile changes such as display name need their own save confirmation. Email changes and account deletion, when enabled, use dedicated confirmation flows; read the stated consequences before confirming. Do not treat them as ordinary profile text edits.

Only enabled actions are available. Placeholder or disabled controls for avatar upload, two-factor authentication or session management do not establish that those capabilities are implemented. Sign out ends access to the current session; confirm your work is saved first.