Find these under Settings → Security, or through Account & security in your account menu.
Everything on that page is per-account, not per-organization. The panel says so directly:
These settings protect your ARRIVE account, not just this organization. ARRIVE is one account across the marketplace and Organization OS, so a password or authenticator app you set here applies — and is required — in both.
That’s the thing to internalise: there is one ARRIVE identity. Changing your password here changes the password you use to browse and book performers, and vice versa.
The page also shows Your role in the organization you’re working in — the role names exactly as your organization shows them. If your role changes, this line follows it, and you’ll get a bell and an email telling you.
Two-factor authentication
Two-factor is optional, and it’s a 6-digit code from an authenticator app — 1Password, Google Authenticator, Authy, or any equivalent.
To turn it on, press Turn on two-factor. You’ll get a QR code to scan, plus the same key in text form if your app can’t scan. Your authenticator will show an entry labelled ARRIVE with your email address, and a rotating 6-digit code. Type the current code and press Confirm & turn on. The card then shows On and the date you added it.
Once it’s on, you’re asked for a code every time you sign in — to the workspace and to the marketplace, because they’re the same account.
To turn it off, use Turn off two-factor. Removing a factor requires a session that has already passed the two-factor check, so if you turned it on in a session that hasn’t, you’ll see:
Could not turn off two-factor. Sign out and back in (entering your code), then try again.
There are no backup codes
This matters, so it’s on the screen too:
There are no backup codes — if you lose your authenticator, support has to verify you and remove it. Keep a second device or your app’s own backup enabled.
There is no self-serve recovery. If you lose the device, you contact support and we verify your identity before removing the factor. Please set up your authenticator app’s own backup, or add ARRIVE to a second device, before you need it.
Deleting an organization needs a two-factor sign-in
If your account has an authenticator set up, deleting an organization requires a session that has passed the code check. Signing in with just your password isn’t enough:
For your security, sign in with your authenticator code before deleting an organization.
Sign out, sign back in entering your code, then try again. (Accounts with no authenticator are unaffected — the typed-organization-name confirmation still applies to everyone.)
Setting or changing your password
A password is optional. Under Password (optional), press Email me a link to set or change your password. We email you a one-time link; follow it and choose a password of at least 8 characters, with a letter and a number. The same link works whether or not you already have a password — there’s no box asking for your current one.
When it saves, every other signed-in session is ended — which is exactly what you want if you’re changing it because something looked wrong.
Signing out other sessions
Sign out other sessions ends every other session on your ARRIVE account — other browsers, other devices, and the marketplace — while keeping you signed in where you are. Use it if you’ve signed in on a shared or borrowed machine, or if you think a session may have been taken.
What this does not do yet
There’s no session list and no sign-in history. You can end all your other sessions, but you can’t see them. The panel is direct about why:
A per-device session list and a full sign-in history aren’t available yet. Supabase doesn’t expose them to an application — reading them needs a database-level change we haven’t made, and we’d rather show nothing than a list we can’t stand behind. “Sign out other sessions” above ends them all regardless.
The Sessions card does show when the current session started, which is the one fact we can report honestly.
A factor added in the marketplace may take up to about an hour to be noticed by a workspace tab you already have open. Turning two-factor on inside the workspace takes effect immediately. Turning it on in the marketplace app writes to that app’s session, so an Organization OS session that’s already open picks it up at its next token refresh — roughly an hour — or at your next sign-in. Sign-in is always current, which is the case that matters: a stolen password can’t open a fresh session without the code. If you want the change reflected right now, sign out and back in.
Related: Inviting people to your organization · Roles and what each one can do.