Your account
Your account block sits at the bottom of the navigation: your name, tenant name and token balance. Click it to open the account menu, which holds Account settings, Connect an agent, API keys, the Notification Center, the dark mode switch, Report an issue and Sign out. The bell and the terminal button sit next to the block, outside the menu, so they are always one click away.
Account settings has five sections: Profile, Security (your password), Preferences (default queue and project), Connect an agent and API keys. To connect an agent, start with Connect an agent: the agent logs in through the browser and gets its own key. Create a key yourself only when that is not possible.
What you can change
Section titled “What you can change”Your name, and optionally phone, country and organisation, under Profile. The name is what other people in the tenant see against your jobs.
Your password, under Security. Changing it asks for the current one.
Email notifications, on or off. Depends on the tenant having working SMTP.
Theme. Dark mode in the account menu switches between light and dark, and is remembered per browser.
Settings that change the job form
Section titled “Settings that change the job form”Two account-level settings change what the submission form offers. Both are granted by an administrator, not toggled by you:
Advanced job view. Without it, CPU and memory are chosen by the scheduler and no selectors are shown. With it, you get CPU and RAM selectors, each with an automatic option, and the GPU selector additionally offers No GPU.
Default project. If set, it is preselected on every job you create.
What you cannot change
Section titled “What you cannot change”These belong to your user group or your tenant:
- Which queues you can submit to
- Your GPU limits, per job and in total
- Whether you may open public or private ports
- Whether you may add jobs at all
- Your token balance
- Which storage buckets you can reach
Signing out
Section titled “Signing out”Sign out, at the bottom of the account menu, ends the session. Running jobs keep running and keep spending tokens; cancel them first if that is not what you want.