Manage your own credentials and browser sessions in Personal settings → Account. Administrators configure server-wide authentication policy separately.
#Review signed-in devices
- Open Personal settings and choose Account.
- Find Signed-in devices.
- Select Manage sessions.
- Identify This session before signing anything out.
- Review browser/device information, last observed activity, IP, and expiry.
- Choose Sign out for the intended entry and confirm.
You can also sign out other sessions through the offered control. Signing out the current session returns you to sign-in. Merely expanding the device list stays inside settings.
Older migrated sessions can show Unknown device or Previous activity unknown. These are missing historical metadata, not evidence of a particular device or login time.
Sessions expire, so an older browser tab may ask you to sign in again.
#Passwords and PINs
Account settings shows whether you use a PIN or password. Choose its Change control and complete the verification shown.
An administrator can switch account sign-in from PINs to passwords. This change cannot be reversed through the policy control. At your next sign-in, use your existing PIN to enroll a password, then use the password for normal access.
A legacy single-user Server PIN is separate from multi-user account authentication. Do not try to repair an account login by changing an unrelated Server PIN.
#Passkeys
Where configured, choose Manage passkeys. Password-enrolled accounts can register, name, rename, and remove passkeys. Management requires fresh password verification and your browser or device's verification.
Use the sign-in address configured for passkeys. If you open Clay Studio through a different hostname or tunnel, a passkey may not work there; use password fallback and ask the administrator to check the passkey settings.
Password fallback remains available. Recovery can clear passkeys and invalidate affected sessions. TOTP authenticator enrollment is not part of this supported flow.
#Resolve sign-in problems
Use the server's actual sign-in URL, check HTTPS and account policy, and distinguish an expired browser session from provider authentication. Your coding-agent login does not sign you into Clay Studio.
See Users and roles, Server settings, and Provider authentication.