TestOrchestrator

Profile

Your name, photo and sign-in email — what other people in the workspace see, and how you get in. The page also states, without letting you edit them, the three facts that decide what you can reach.

Profile photo

Your photo is shown next to your name on runs, comments and assignments. The page states the rules next to the picker: PNG, JPG, WEBP or GIF, up to 2 MB, cropped to a square. Until you upload one, the circle shows your initials.

Choosing a file previews it. Nothing is uploaded and nothing is stored while you are still deciding — the save bar simply switches to Unsaved changes, and the upload happens when you press Save changes. Press Discard instead and the picked file is dropped, having never left your machine.

  • A file of the wrong kind is refused on the spot: “Use a PNG, JPG, WEBP or GIF.”
  • A file over the limit is refused the same way: “That file is over 2 MB. Choose a smaller photo.”
  • Once you have a photo, a Remove button appears beside it. Removing is also a draft — the photo goes when you save, and Discard puts it back.

After a successful save the confirmation reads Profile saved, and the new photo appears immediately everywhere it is drawn, including your own account tile in the sidebar. There is no reload to wait for.

Full name

Full name is how you appear to everyone in this workspace. It accepts up to 255 characters.

The name cannot be emptied: saving with the field blank marks it as invalid, answers Name is required, and writes nothing. Fix the field or press Discard.

Sign-in email

Your sign-in address is shown as a fact rather than an editable field, because changing it is not a save. Beside it sits a small button tooltipped Change sign-in email, and the row explains what a change involves before you start it: “Confirmed from two inboxes, and it signs you out when it completes.”

Starting the change

The button opens a dialog headed Change sign-in email, subtitled Two confirmations, from two inboxes. It takes the New email, reminds you what your current address is, and numbers what will happen before you commit to any of it:

  1. We email your current address a link to approve the change.
  2. We then email the new address a link to finish it.
  3. The change completes and this session signs out.

Choose Send confirmation link and the dialog becomes Check your inbox: it confirms which address the first link went to, marks that step done, and leaves the remaining two showing what is still to come. It closes with Done — and says so plainly: “You can close this — it continues from your inbox.” Closing the dialog does not cancel anything.

Both links are needed, and the second one signs you out. Until you have followed the link in your current inbox and the link sent to the new address, your sign-in address is unchanged and you keep signing in with the old one. When the second link completes the change, the session that started it ends and you sign in again — at the new address.

While a change is in flight

A banner sits above the page for the rest of your visit: “Waiting for <new address> to be confirmed. Until then your sign-in address is still <current address>.” It carries a Resend button, which sends the approval link again.

The banner belongs to the visit, not to the account: reload the page and it is gone, even though the change is still pending. Nothing has been cancelled — the links in your inbox still work. If you would rather start over, open Change sign-in email again and send a fresh pair.

If your current address is not verified

A different banner appears when the address on the account has never been confirmed: “<address> is not verified, so we cannot send sign-in links to it. Changing it below sends a fresh link you can confirm.” This one has no Resend button; the way out is to run a change and confirm the new address.

There is no password here. Signing in to TestOrchestrator is by emailed link and one-time code, or through Google, GitHub or your workspace’s SSO provider — so your sign-in email is the whole of your credentials, and there is nothing on this page to reset. See Log In.

Your access

The lower panel states three facts and lets you change none of them:

  • Workspace — the workspace you are signed in to
  • Role — your Role, which decides what you can do inside projects
  • Access level — your Access Level, which decides how much of Settings you can administer

The panel says where they come from: “Set by a workspace admin in Users & access. Ask there if something looks wrong.” A Tenant Admin changes them from Settings → Users.