Workspace settings

The Workspace screen, for the admin role, is what the workspace is as opposed to what is kept inside it: the zone that decides when everything runs, and who the workspace belongs to.

Timezone

Every workspace has one zone, and every schedule in it is evaluated there. It is chosen at registration and changed here; a workspace that never chose is in UTC.

The picker lists every zone your browser knows, grouped by region, and under it is the check that makes the choice verifiable: the current time in the zone you have selected. Somebody who cannot tell Europe/Prague from Europe/Bratislava can tell 14:32 from 08:32.

What a change moves

Every schedule keeps the time it is written with. 0 3 * * * still means three in the morning — from now on, three in the morning in the new zone. So a job does move in absolute terms: going from UTC to Europe/Prague in summer, a nightly job runs two hours earlier than it did yesterday.

What does not happen is the other possibility, and it is worth stating because it is the one people expect: Runjet does not rewrite your schedules to keep their old absolute times. A job you wrote as three would start reading Daily at 01:00 in the list, and a schedule that changes under you is worse than one that moves.

The confirmation says so before anything happens, and the change is undone by choosing the old zone again.

What a change does not touch

• Runs that have already happened. Their times are instants, and an instant does not move; the same moment is simply written differently on screen.
• Runs in flight. They live on their agents and report back regardless.
• Missed runs. A change would otherwise look to a job with catch-up like an outage — the occurrence for today may already have passed in the new zone — so Runjet puts a floor under catch-up as it applies the change, and nothing is made up that never was.

Times on these screens

Every time Runjet shows you — the run history, what is next up, the audit log, the clock in the header — is drawn in the workspace's zone, not your browser's. One zone across the product: a history in your zone beside a schedule in the workspace's would be two clocks disagreeing on one screen, and the history's date filter would cut the day at a different midnight from the one your jobs fire on.

The zone is named where it matters rather than on every row — beside the run history's date filter, and on the header clock.

Who may change it

An admin, and nobody else (roles). Changing this moves when every job in the workspace runs, which is a larger act than deleting one job — already an administrator's. Every change is a workspace.timezone row in the audit log, naming both zones.

A suspended workspace refuses it with a 402, like every other change: it is not scheduling, so changing when it would schedule buys nothing.

Who the workspace belongs to

Three answers, chosen at registration:

It decides which terms apply to the workspace and whether consumer protection does. There is no default and nothing is preselected, because the three answers have different consequences and a guess would be a decision made for you.

It is not a tax status, and Runjet never treats it as one. A sole trader below the VAT threshold is in business and has no VAT number; a company that gives no number at the checkout is still a company. VAT is decided at the payment provider, from what you enter there, and neither is derived from the other.

The registration number

Whatever your own register knows you by — a company number, a business ID, an EIN. A company has one, so it is required; a sole trader may not, so it is optional; an individual has none, and the field is not shown.

We record it. We do not check it. Runjet is sold worldwide and there is no register it could be checked against, so it is your statement rather than something we confirmed — and nothing in the product says otherwise.

Changing it

An admin, until the workspace has been paid for. After the first payment the screen shows what the workspace is and no longer offers to change it: who a paid-for workspace belongs to is part of an agreement rather than a setting, and changing it means writing to us. The API answers 409 either way, so the missing control is a courtesy and not the rule.

Every change is a workspace.legal_form row in the audit log, naming both answers.