Accounts

Accounts

Argosy can hold more than one RomM account on the same device. Add a second account, switch between them, and each one keeps its own saves, achievements, and view of the library, without signing out of the first.

This page covers what is shared across every account on a device and what stays private to one. For how saves themselves behave, see Save Sync.

Adding an account

Add an account from the account row at the top of the drawer, or from Settings > RomM > Accounts > Add Account. You need to already be signed in to a RomM account; the new account pairs against that same server, there is no separate URL step.

Pairing a second account always uses device-managed registration: Argosy shows a QR code and a short code, you approve the device from the RomM web UI while signed in as the account you want to add, and Argosy signs in as them once approved. This is the same method the first-launch wizard uses on RomM 5.0+ servers. There is no fallback to the older 8-character pairing code for a second account, so adding one requires a server that supports device-managed registration.

Adding an account does not switch to it. You stay signed in as whoever was active, and switch explicitly when you are ready.

Signing into a different user or a different server from Settings > RomM > Rom Manager is a separate flow, not this one. That screen still behaves the old, single-account way: it replaces the one stored connection, purges the local RomM library on a user or server change, and refuses if you have saves waiting to upload. Use Add Account when you want a second identity that coexists with the first instead of replacing it.

What stays with one account

• Save files, save states, and their sync and ownership records
• RetroAchievements login and unlocked achievements
• Favorites, hidden games, ratings, difficulty, completion status, backlog and "now playing" flags, play count, total play time, and last-played date
• Which RomM collections you belong to
• Sync and download work that account queued but has not sent yet
• Sync filters (region priority, exclude beta/prototype/demo/hack) and per-category download defaults
• Look and feel: theme, colors, background, fonts, box art style, UI sounds, and background music
• Social and QuayPass identity, where linked

What is shared across every account on the device

• The RomM library itself: the game list, box art, and platform structure come from the server and are not duplicated per account
• Which platforms sync at all (Platform Filters)
• Save Sync and Secure Saves toggles, the local save cache limit, and any custom save/state path overrides
• Screenshot and 3D box art caching, and screenshot uploads
• Everything tied to the physical device rather than a person: ambient LED, dual-screen and display-role settings, the screen dimmer, UI scale, controller mapping, installed emulators and cores, and BIOS files

Switching accounts

Switching archives the outgoing account's saves and states off their on-disk paths, verifies the archive, then places the incoming account's own copies back, so the two are never mixed on disk even though they can share the exact same save path. This runs one file at a time and is resumable: if Argosy is killed mid-switch, it picks back up where it left off the next time it starts.

A switch is blocked while a game session is open (including one launched outside Argosy that was recently on screen), or while a download, an emulator install, a Steam download, a library sync, or a netplay session is running. Argosy asks you to confirm that anything launched outside itself is actually closed, since it has no session record for those.

If the incoming account's only local copy of a save or state was known to be older than the server's, the slot is left empty on purpose rather than guessed at. The Accounts screen lists which titles are waiting, and the next sync fills them in.

Queued upload work follows the account that queued it, not whoever is currently signed in, so background sync never sends one account's saves under another's name.

Removing an account

Removing an account deletes everything listed under "What stays with one account" for it, after archiving any saves and states it still holds on disk. It does not delete the shared RomM library, and it does not revoke the account's device registration on the RomM server; there is no client-side path for that, so remove it there by hand if you want the device fully forgotten.

You cannot remove the active account; switch to another one first. If the account being removed has unsent queued work, Argosy shows what it is and asks whether to discard it or keep it and cancel the removal.

Upgrading from a single-account install

If you already had a RomM account signed in before v2.5.0, it is adopted automatically the first time Argosy opens after updating. Your existing saves, save states, play history, achievements, and queued sync work are all attributed to that account with no action needed, and nothing is duplicated into a second account.

Testing status

Multi-account support is new in 2.5.0. The upgrade path above was checked in testing and should look and behave exactly as it did before. Switching between two or more accounts, and how per-account settings interact with per-account saves, is new and has had less exposure. If you see a save under the wrong account, a sync that stalls after switching, or a setting that seems to follow you across accounts when it should not (or the reverse), please report it.