Account setup
Four account settings to check before your first job. Most jobs that fail immediately fail for one of the reasons on this page.
Sign in
Rescale runs entirely in the browser, with nothing to install. Which URL you sign in at depends on your organization's platform. See platform regions.
How you get an account depends on your organization:
If you don't have an account, ask your organization's Rescale admin to invite you. Signing up independently won't attach you to your company's workspace, licenses, or budget.
Multi-factor authentication
MFA is required for every Rescale user whose organization doesn't use SSO. On first sign-in you'll be prompted to enroll; email is the default, and you can add an authenticator app instead.
Generate backup codes while you're there. See MFA.
If your organization uses SSO, your identity provider handles the second factor and you don't enroll separately.
Know which workspace you're in
Your account lives in an organization, which contains one or more workspaces. The workspace determines your available software, hardware, policies, and budget, so the same account can see different options depending on which one is active.
The workspace switcher is in the top right. If software or hardware you expect is missing, check it before assuming an entitlement problem.
See organizations and workspaces for the full model, and core concepts for how projects and groups fit in.
Confirm you can pay for a job
On submission, Rescale runs a billing precondition check confirming the first hour of the job can be paid for. A workspace with no credit, no deposit, and no card on file fails this check, and the job never starts.
This is the most common cause of a first job failing instantly. It isn't a problem with your model.
You need one of: available credit, a deposit, or a valid credit card on the workspace. If you're not an admin, ask yours: see budgets and deposits.
Also worth checking if you're on a workspace with budgets configured: a budget that's exhausted or set to strict enforcement will block submission the same way.
Set a default workspace
If you belong to several workspaces, set the one you work in most as your default so you don't have to switch after every sign-in: Preferences → Default Workspace.
Get an API key and the client tools
You need a key for the CLI, the REST API, or the Transfer Manager.
Preferences > API → Add API Key.
Two things worth knowing:
- You can hold more than one key. Keys you create do not expire by default. If your organization has set a maximum key lifetime, keys created after that policy takes effect show an expiration date, and a key that stops working may simply have expired. See API keys for the full behavior.
- The Transfer Manager and CLI download from this same page. The CLI offers Latest, Beta, and Previous versions with a platform picker.
Also worth doing now
An SSH key, if you'll want a terminal into a running job or workstation. Register your public key once and every cluster you launch afterwards accepts it: see SSH access.
Your own software licenses, if you're not using on-demand licensing. See licensing.
Then run something
You're set up. Your first job takes it from here.
Related
- Your first job — the next step
- Core concepts — organizations, workspaces, projects
- MFA · SSO
- Budgets and deposits — what the precondition checks