How to use Skarrow, in plain language

Getting started

• Create your account. One step at /register: name, email, a strong password and the terms. The account provisions one private workspace that is yours alone.
• Open the workspace. The dashboard at /app shows your plan limits, recent searches and shortcuts. The left sidebar is the map of the whole workspace.
• Set your defaults once. Under Settings, choose your default country (Indeed country code), a preferred location, results per board and the posted-within window — every new search in the console prefills from these.

Searching the employment platforms

• One form reaches every selected board. In Job Search, enter the search term and location, pick sources from the 21-board list, and run the search once. Every answer lands in one normalized table — nothing re-queries the boards while you explore.
• Country codes are for Indeed. The country field (usa, uae, gbr…) applies to Indeed only; the other boards take the location text.
• Board failures stay honest. A rate-limited or blocked board reports its real error beside the results, and the other sources keep working. Wait a minute, trim the board list and run again if a board throttles.
• Every run is recorded. Each execution becomes a row in Search History with its own record — open it later to see exactly what it found. Re-running the identical search reuses the stored run and does not consume quota again.

Filters, sorting and exports

• All narrowing is local. Keyword filter, source multi-select, remote-only and salary toggles, plus per-column sorting run in your browser against the run's stored results.
• Inspect before you commit. Click any row to expand the inspector: full description, salary, posting date and the direct link to the original listing.
• Export carries every field. The CSV export contains every column the boards returned — descriptions included — narrowed to whatever filters are active. The export note tells you when filters trimmed the file.

Managing saved jobs

• Save from a run. In the results, save a listing straight from its row into your collection. Saving is idempotent — re-saving the same listing never creates a duplicate.
• Notes stay with the listing. Add private notes to any saved job; they belong to your workspace only.
• Plan limits apply honestly. The Free plan keeps up to 100 saved jobs; when the collection is full the save is refused with the reason — remove one or upgrade to Pro.

Search history

• History is per account. Only your runs appear, newest first, with the boards, term and result count.
• Reopening is free. Opening a stored run replays its saved dataset; it never spends quota or re-queries the boards.
• Delete what you do not need. A run can be removed from history; other users can never see or delete yours.

Applications and alerts

• Track from a listing. Start tracking an application from a saved job or a search result; the pipeline moves through planned, applied, interview, offer and closed states with a history of every change.
• Alerts watch saved searches. Save a search as an alert (daily or weekly) and the scheduler checks it on the database clock — the same checks you can trigger with "Run now". New listings are announced once; the same listing is never announced twice.
• Alert runs respect your plan. Alert checks go through the same quota, spacing and per-account lock as console searches.

Account and billing

• Your plan, enforced server-side. Monthly Usage and Plan & Billing read the same entitlement service the server enforces — the pages cannot drift from reality. Free accounts see every limit on the dashboard.
• Paid plans activate only through verified webhooks. If billing is not configured on a deployment, checkout says so plainly and your current plan stays fully usable.
• Password recovery. "Forgot password" sends a single-use, one-hour link when email is configured. Without email, an operator issues the link from the host — the app never pretends an email was sent.
• Sessions. "Keep me signed in" lasts up to 365 days on that device; logging out ends the session. The Security page lists every active session and can sign out any or all of them — see the workspace's Security settings.

Troubleshooting

• "Read timed out" / 429 errors. The board throttled or stalled. Wait about a minute, trim the source list, and run again — errors stay per-board, so other sources still return their results.
• Empty salary column. Many boards return salary data unevenly; the dash means the source did not provide one. Tick "Fetch descriptions" for richer rows.
• Corporate networks. Several boards block datacenter IPs; the optional proxy field in the advanced section handles that case.
• "A search is already running" (429). Your previous execution is still in flight — one live search per account at a time. It never blocks another account.
• Missing results? Check the per-board warnings under the results: a board that returned nothing says so explicitly instead of failing silently.

This page describes the shipped product only — features that are not released yet are marked "soon" in the workspace instead of being promised here. Something missing? Tell the team.