Account & organizations
Everything self-service about your identity and your tenants lives on three settings pages: /app/account for you, /app/:org/settings for an organization, and /app/:org/:project/settings for a project. Each follows the same shape — General at the top, feature cards in the middle, and a Danger zone at the bottom.
Your account
- +Display name — optional. Without one, EvalShift labels you by your email address.
- +Email — changing it is double opt-in. The new address gets a confirmation link; the old one gets a notice. The account does not move until the new address confirms, and requesting again retires the previous link.
- +Password — changing it signs you out everywhere else and burns any password-reset link still in flight. The tab you are standing in stays open. If you signed up with GitHub you have no password yet; the same card offers to set a first one.
Organizations & projects
- +Names are editable; slugs are not. A slug is baked into URLs, CI configs,
evalshift.yaml, uploaded bundles and API key scopes, so renaming one would break every reference to it. Renaming the human-facing name is free and takes effect immediately. - +A deleted slug stays taken. It is not released for reuse, so recreating something under the same slug is rejected. Pick a new one.
- +Editing needs a permission, not a role. Owners and admins can rename; deleting an organization is owner-only. See Roles & permissions in your org settings for the full matrix.
What deletion removes
Every destructive action asks you to type the resource’s slug — or, for your account, your email address, plus your current password if the account has one — before it will run. None of them can be undone from the app.
| Action | Removes | Keeps |
|---|---|---|
| Delete a project | The project and every run, trend, baseline and share link under it. | The rows themselves — the project is hidden, not erased. |
| Delete an organization | Every project in it, its API keys and service accounts, and its Stripe subscription. | The audit log and billing history, which the org's rows are attached to. |
| Delete your account | Your sign-in, your API keys, every session, and any organization you are the only member of. | Runs, comments, baselines and share links you created — with your name removed. |
Organizations you are the only member of are different: they are deleted along with your account, including the personal organization EvalShift created for you at signup. If one of them has a paid plan, its subscription is cancelled first — and if that cancellation fails, nothing is deleted at all.
What happens to API keys
- +Deleting an organization revokes every key scoped to it, including the ones its service accounts own. CI jobs using them start failing immediately.
- +Deleting your account revokes the personal keys you own. Keys belonging to a service account are unaffected — they belong to the organization, not to you.
- +Being removed from an organization revokes only the keys that were pinned to it. An unscoped personal key keeps working elsewhere; it simply stops reaching that organization.
If your account is suspended
EvalShift can suspend an account. While it is suspended, every signed-in page shows Your account is suspended instead, sign-in is refused, and the API answers your personal keys — and so the CLI — with a 403. Nothing is deleted: your keys, memberships and runs stay as they were, and the keys work again once the suspension is lifted (the web app needs a fresh sign-in). Service-account keys belong to the organization, so its CI keeps running. If you think it is a mistake, email [email protected].