Learn

Architecture & pattern guides

Read the idea, build it on a Grid, prove it in a challenge. Short, practical guides — illustrated with RodGrid's own nodes — on system design, design patterns, flow modeling, and how to get the most out of the app.

All articles

Your account: signing in, two-factor, and why you were signed out

There is no password to lose. What there is: an optional second factor, an idle clock on live Grids, a ceiling of two signed-in browsers, and sign-ins that run out.

The sign-in screen offers three ways in: Continue with GitHub, Continue with Google, and Email me a sign-in link. None of them asks for a RodGrid password, because RodGrid stores none: there is no password here to reuse, reset or leak. Without two-factor, whoever gets into the email, GitHub or Google account you sign in with can get into RodGrid too; two-factor, below, is what changes that. The emailed link is for the machine where you can't use GitHub or Google, such as a work laptop. It works once, for fifteen minutes. Opened in the browser that asked for it, it signs you in; opened in any other, it first asks you to press Continue as followed by your address, so a link someone forwards you cannot quietly sign you into their account.

Should you turn on two-factor?

If anyone else could get into your email, your GitHub or your Google account, yes. It is optional and free on every plan. Once it is on, each sign-in, by any of the three routes, stops at Two-factor verification and asks for the 6-digit code from your authenticator app. Getting into your mailbox is then not enough to get into RodGrid. Setting it up takes a minute:

  1. Open Profile, find Two-factor authentication and press Enable 2FA.
  2. Scan the QR with an authenticator app such as Google Authenticator, 1Password or Authy. The QR is drawn in your browser, so the secret is never handed to a third-party image service. If you can't scan, type the key shown under it into the app's manual-entry option, or use Copy setup link, which copies the whole setup as a link for an app that lets you paste one.
  3. Type the 6-digit code the app shows and press Confirm and enable.
  4. RodGrid shows ten recovery codes, once. Save them with Download codes, then press Done. RodGrid keeps only their hashes, so it cannot show them again.

Instead of the QR, Enable 2FA may answer that two-factor can only be turned on within 15 minutes of signing in. Sign out, sign back in, and try again: an older sign-in, if stolen, cannot enrol someone else's authenticator, though one stolen within its first 15 minutes still could. The same rule guards changing your email, exporting your data and deleting the account. Turning two-factor on also signs out every other browser on the account, so a session someone took before you added the second factor does not outlive it. Changing your email does the same.

Watch outEach recovery code works once, at Use a recovery code instead on the sign-in step, and those ten are the only copy. Keep them somewhere that is not the phone holding your authenticator and not the account they unlock: a note inside RodGrid is out of reach exactly when you need it, and a password manager that also holds the second factor is no backup if that phone is the only way into it.

Turning it off, with Disable 2FA, asks for a live code or one of those recovery codes. Being signed in is deliberately not enough, because a stolen session should not be able to remove the thing protecting the account.

Why you were signed out, or sent back to the dashboard

Start with where you landed. On the dashboard, still signed in: that is the idle clock, and it only runs on a Grid open in the editor. Twenty minutes without a mouse move, click, key, touch or scroll brings up Are you still there? with a sixty-second countdown, and any movement, or I'm still here, cancels it. If it runs out, the Grid closes and you land on the dashboard — still signed in. A top bar showing Reconnecting… is a different thing, a dropped connection, and Sharing & realtime collaboration covers it.

At the sign-in screen: one of these ended the sign-in in that browser.

  • A third browser signed in. An account may be signed in on two browsers at once, and a third sign-in ends the oldest one, never the newest. If the evicted browser has RodGrid open, it usually says so: "Your account was opened on another device, so this session was signed out."
  • Two-factor went on, or the email changed, somewhere else. Both sign out every other browser. An open one usually says that "Your account's security settings were changed in another session".
  • The browser sat unused. A sign-in nobody uses runs out within two weeks of the last time it was used.
  • Thirty days passed. However often you use it, a sign-in ends thirty days after it started, and you sign in again. Why a server session has both an idle limit and a hard one is in Sessions vs tokens: JWT, refresh & revocation.
NoteThe unit of the two-browser ceiling is a browser, not a tab: every tab of one browser shares one session, so opening twenty of them costs nothing. A private window is a different browser, and so is your phone. A browser whose sign-in has already run out no longer counts. The ceiling is two on Free, Pro and Premium.

There is no "sign out everywhere" button yet. If a third tab opens on the sign-in screen, the tab is not the cause, since tabs share one sign-in: check the list above, starting with a phone or private window that signed in after this browser.

No Challenge drills these settings, but the Distributed Session Store Challenge has you build what sits behind them: sessions that expire after a TTL, and a logout that reaches every node, including the copies app servers cache locally.

Practice this