Account settings fields
Your own settings, under Settings. They follow you across every organisation you belong to.
Profile
| Field | Notes |
|---|---|
| Name | How you appear to others in your organisations |
| Your sign-in address |
Security
Your password, and the other means of signing in your account supports.
Changing your password affects your account, not any organisation. It does not sign other people out of anything.
Sessions
The devices and browsers currently signed in as you. Ending one signs that device out.
Yours only. You cannot see or end another member's sessions here — removing someone's access to an organisation is a membership change, not a session one.
Notifications
Which notifications you receive.
Per person, not per organisation. Two admins in the same organisation can be notified about completely different things, and neither setting affects the other.
Worth remembering when nobody noticed something: usually nobody had that notification switched on, rather than the organisation being misconfigured.
API keys — not personal
| Field | Notes |
|---|---|
| Name | Your label for the key |
| Key | Shown once, at creation. Never displayed again |
| Last used | When it was last seen |
| Revoked | Marks a key as withdrawn; the record is kept |
A key authorises access on behalf of the whole organisation, not on behalf of you. The screen sits with your personal settings, which makes it easy to assume otherwise.
That assumption matters: a key that leaks reaches the organisation's data, not just yours.
The plaintext is shown only at creation — Yessort stores a hash and cannot show it to you again. Lose it and you create a new one.
Revoking keeps the record rather than deleting it, so the history of what a key did and who withdrew it survives.
See create an API key.
Not here
Organisation settings — members, roles, billing, the audit log — are under the organisation, not your account, and need organisation-admin access. See your account and your organisation.