Adjoint Docs Product ↗
Menu

Account and sessions

Managing your own login — profile, password, and active sessions. This applies the same way to admins and developers; there's no separate "admin account" surface.

Viewing your profile

$ adj account view
Email:        [email protected]
Name:         Dana Lin
Role:         user
Status:       active
Org:          acme
Member since: 2026-06-02T14:03:11Z
ID:           usr-7f2a

adj account with no subcommand runs the same thing.

Setting your display name

$ adj account set-name "Dana Lin"
Name set to "Dana Lin".

Changing your password

$ adj account set-password
Current password: ********
New password: ********
Password changed. Other sessions were signed out.

The current password is always read from an interactive, no-echo prompt — never from an environment variable, so a compromised environment can't silently rotate your credentials. The new password comes from the ADJ_NEW_PASSWORD environment variable if set (handy for scripting a rotation), otherwise another no-echo prompt.

Changing your password revokes every other session — anywhere else you're logged in gets signed out. The session that made the change stays signed in, so you're never locked out by your own password change.

Sessions

$ adj account sessions
ISSUED                EXPIRES                CURRENT  ID
2026-07-10T09:12:00Z  2026-08-09T09:12:00Z    *        sess-1a
2026-06-28T16:40:00Z  2026-07-28T16:40:00Z             sess-9c

The CURRENT column marks the session you're issuing the command from (*). If you see a session you don't recognize, that's a sign to change your password (it revokes every session but the current one) or sign out everywhere.

Signing out

$ adj logout

Plain adj logout revokes the current session's refresh token server-side and clears your local tokens. It's idempotent — running it twice is fine. Your server, org, and email stay in the local config, so logging back in is one command (adj login).

$ adj logout --all

--all revokes every session for your account server-side, not just the one you're running the command from — use it if you suspect a token leaked, or you're offboarding your own access from a shared machine.

Next