Signing in to Omniscio (and having one account, not two)
The sign-in screen you meet before Omniscio opens, plus the matching card at Settings → Accounts. It is separate from the Claude/Anthropic login that runs your sessions — this one is your Omniscio account, and it is what your plan, your team, and cloud sync hang off.
On this page
What it is
Status: shipped. Sign-in is required — there is no "skip" button on any build. Today the way in is Google, email + password, plus GitHub (only where it is configured). Desktop only; a phone signs in by pairing with a desktop that already did. Contract: global-auth-gate-contract.
The email door is OPEN (owner decision 2026-10-15, re-opening the 2026-08-31 hold). The form, "Forgot password?" and account creation are all live, and everything below about the email door describes what you see today. If the door is ever held off again it is one boolean in shared code, and the same paragraphs below then read as "when it is on".
While a browser sign-in is running the card says so, tells you a closed tab can be reopened by pressing the sign-in button again, and offers Cancel to abandon it. A browser-side refusal reads as plain English — declining at Google shows "Sign-in was cancelled." — never as a raw provider error.
The sign-in screen you meet before Omniscio opens, plus the matching card at Settings → Accounts. It is separate from the Claude/Anthropic login that runs your sessions — this one is your Omniscio account, and it is what your plan, your team, and cloud sync hang off.
Where to find it
The sign-in screen that appears before Omniscio opens, plus the matching card at Settings → Accounts.
How it behaves
One address is one account
Omniscio allows one account per email address. That is a deliberate setting, and it is the thing to understand if you ever wonder why two sign-in methods land you in the same place: they are supposed to. Signing in with Google and signing in with your email and password, at the same address, open the same account — same projects, same plan, same history.
If you signed up with Google and then try email + password
This is the common case, and it used to trap people.
A Google account has no password. Google vouches for you, so Omniscio never asked you to choose one. So if you later type that same address into the email form:
| You try | What happens |
|---|---|
| Create account | "That email already has an account" — because it does, via Google |
| Sign in | It fails — there is no password on that account yet |
Neither is a broken account. You have two ways forward, and the screen now names both:
- Use the Google button. Instant, and it is the account you already have.
- Choose "Forgot password?" and set one. Despite the name, this works even though you never had a password — it adds one to your existing account. Nothing is replaced, and your Google sign-in keeps working.
Adding a password on purpose (Settings)
If you would rather not wait for an email, and you are already signed in:
Settings → Accounts → Linked providers → Email + password → Set a password.
Pick a password of at least 12 characters and save. From then on either door opens the same account. The row reads Connected once you have one.
This is desktop-only on purpose. A phone paired to your desktop is deliberately not allowed to create a password for your account — if that pairing link ever leaked, it would hand whoever had it a permanent way in that survives un-pairing.
If Omniscio cannot reach its sign-in service at launch
A failed refresh at launch is not a sign-out. If you were signed in last time, Omniscio keeps you signed in and opens normally — including after more than a day offline. It keeps re-checking in the background and signs you out only when the sign-in service confirms the stored credential is genuinely dead (for example, a disabled account or a revoked session), and that confirmation also raises a notice explaining why.
Your plan does not fall back to Free while you are offline. The plan you last confirmed keeps applying on this computer, so locally gated paid features keep working; cloud features need a confirmed sign-in, and the app asks you to sign in again when it cannot confirm one. That request is not only an inbox message: a banner across the top of the window says Omniscio can't confirm your account and offers Sign in again (it goes to the same control under Settings → Accounts). The banner comes back each time you open the app for as long as the problem lasts, hides for the session when you dismiss it, and honours the per-alert switch under Settings → Inbox → Alert pop-ups if you would rather turn this banner off entirely. The notice stays in your inbox either way, as the permanent copy of the warning. The first successful reconnection renews the sign-in silently, and the notice clears itself once your account is confirmed again — taking the banner with it.
That holds for a sign-in too: if the plan check itself cannot be reached when you sign in, the plan you last confirmed is the one that stays — a check that could not be made is never taken as evidence that your plan changed. The moment the check can be made again, the real plan is applied, including a genuine downgrade.
If you switch accounts while an action is still finishing — linking a provider, setting a password, or saving your profile — Omniscio refuses that action rather than applying it to the account that just signed in.
Your plan after signing in
Right after you sign in, Omniscio confirms your plan (Free / Pro / team / enterprise) against the tamper-proof copy carried inside your sign-in token, because the plan recorded in your account profile is one the app must not take on trust.
That check needs the sign-in service. If the service cannot be reached at that moment, Omniscio does not drop you to Free: it reads the plan from the sign-in token your sign-in had just issued, which is equally tamper-proof. A network blip therefore never costs a paying user their plan.
The one case that still resolves to Free is the one where no tamper-proof copy can be read — a total outage that also blocks the certificates Omniscio checks signatures against, or a computer whose clock is far from real time. Your plan comes back on the next successful refresh, which happens on its own; there is nothing to do and nothing to re-enter. A written plan is never remembered from an unconfirmed source, so a forged plan in an account profile can never stick.
Your email and your name
The Identity card at Settings → Accounts shows your display name, your avatar, and the email address your account hangs off.
The email is fixed to the sign-in identity and cannot be changed in the app. It is whatever Google or GitHub handed over when you signed in, and signing in with a different address does not move your account to it — it makes a new, separate account, with none of your projects, sessions or team access.
If the address itself has to change — a typo, or a mailbox you can no longer reach — use the Need to change it? Contact support button on the card. It opens a pre-addressed message so support can make the change on their side.
Your display name and profile photo are editable: Settings → Accounts → Identity → Edit opens the profile dialog, where you can set the name and upload, change or remove a photo.
Accepting the Terms
After you sign in for the first time — and again whenever the Terms of Service or Privacy Policy change — Omniscio shows a Before you continue screen. Click I Agree & Continue to accept and open the app, or View Terms & Privacy Policy to read them first.
On a dev build (Omniscio run from source in development) this screen does not appear. The released app always asks, including after the Terms change.
If the click cannot take effect, the screen says why instead of doing nothing:
| Message | What it means | What to do |
|---|---|---|
| "We couldn't save your acceptance…" | The acceptance was not saved. | Check your connection and click again. |
| "Omniscio is only partly updated…" | Part of Omniscio is still running an older version, so it saved an older version of the Terms than the screen asks for. | Quit Omniscio on your computer, open it again, then accept once more. |
Sign out on the same screen takes you back to sign-in if you are in the wrong account.
Signing out
Settings → Accounts → Identity → Sign out. It asks you to confirm first, because it ends your Omniscio cloud session and clears the stores that hang off your identity — Team Chat, User Management and Agent Email. You can sign back in whenever you like.
On a shared computer it also wipes what the next person could otherwise see on screen: your open notes, mind maps, flowcharts and decks, your workflows and their run lists, the record of which sessions you have shared and who joined them, your API-key list, Image Studio's recent prompts, and the saved browser data (cookies and local storage) for the share-comments pages. Signing in as a different person does the same. This clears screens and cached copies only; everything you saved is still stored and comes back when you sign back in.
It deletes nothing you saved. Your projects, sessions and settings stay exactly where they are on this machine and are waiting when you sign back in. The only things lost for good are small conveniences kept just in this computer's browser storage: unsaved form drafts and Image Studio's recent prompts.
There is a second sign-out, for the case where Settings is out of reach: if you are stopped at the full-screen sign-in gate — signed in, but not authorized yet, or waiting on an access request — the gate itself offers Use a different account, which is the same sign-out, so you can go back and pick the right identity.
Not the same as signing out of Claude. Removing a Claude or API account (Removing a Claude or API account) forgets an Anthropic credential stored on this machine. It does not touch your Omniscio account.
Why the sign-in error is always vague
Signing in with a wrong password and signing in with an address that has no account give the identical message. That is intentional: a message that distinguished them would let anyone check whether a given person has an Omniscio account, just by typing their address. The same reasoning is why a password-reset request always answers "if that address has an account, we've sent it a link" — it never confirms either way.
When sign-in is refused
Not every refusal is the vague password message. Five other answers name their own cause, and each has its own way out:
| What the screen says | What it means | What to do |
|---|---|---|
| "This account has been disabled. Contact support if that seems wrong." | An Omniscio administrator has switched this account off. It is not your password, your Google account, or your Claude login — every sign-in door is refused while the flag is set. | Contact support with the address you sign in with and this exact message. Support is the only side that can lift it; setting a new password will not. |
| "Your account has been suspended. Contact your admin." | You signed in, but the Omniscio account behind that identity is suspended, so the app will not open. | Contact your workspace admin or support with the address and the message. |
| "Too many attempts. Wait a few minutes and try again." | A short throttle after repeated tries, not a lockout. | Wait a few minutes, then try once. Trying again immediately extends the wait. |
| "Couldn't reach the server. Please try again." | Your account is fine; the app could not finish the call — usually an offline machine, a captive portal, or a dropped connection. | Check the connection (open any web page), then retry. |
| "Too many new accounts from this email provider today. Please try again in about N hours." (or "…from this network today…", or "…from your organisation's email address today…") | A daily ceiling on how many brand-new accounts can be created from one place: one for a public mailbox provider, one for a company domain, and one for a network. It clears by itself; nothing is wrong with your address or your password. | Wait the hours the message names, then sign in again. An existing account is never affected — only creating a new one is. If a workspace invited you, the network ceiling never applies to you — sign in with the address the invitation was sent to. If the message is about the email domain or the provider and a colleague says the same thing happened to them, tell whoever invited you; the inviter can ask support for a higher ceiling for that day. |
| "Account not authorized" (full-screen gate) | You signed in, but this account has no access to this app yet — there is no profile, or access was not granted. | Press Request access, or use the click-to-copy support address on the gate. Use a different account signs you out if you meant another identity. |
The disabled and not-authorized screens carry a click-to-copy support address, so you do not need a mail app: the screen copies the address and you paste it wherever you write from. Who can restore access, and what each role can do, is covered in User Management.
Verifying your email address
A new email + password account is always unverified at first. After you create it, Omniscio shows "Almost there — open the link we sent to …", and the verification email is sent automatically.
Leave the window open. Omniscio keeps watching that sign-up for up to half an hour, and the moment the address is confirmed it lets you in by itself — no second password entry, no button to press. It works the same when you open the link on your phone.
The email comes from Omniscio with the subject "Confirm your email for Omniscio", and
replies go to support@omniscio.com. Its link opens omniscio.com/auth/action, an Omniscio
page that confirms the address and then tells you to go back to the app, where the window is
already letting you in. The email's
text is a few plain lines: Firebase, which sends it, does not let that one message be restyled.
The password-reset email is fully designed and opens the same page, which shows a form for the
new password (at least 12 characters) and then sends you back to the app.
- Nothing arrived? Give it a minute and check the spam or promotions folder. The sign-in form has a Resend verification email button under that notice — use it rather than typing your password again.
- Link expired or already used? Verification links are single-use and time-limited. Resend a fresh one, then click the newest email.
- Typed the wrong address? Choose Use a different email under the notice and start again with the right one. That also stops Omniscio watching the abandoned sign-up, so you are never let into the address you moved on from.
- Still stuck after resending? Sign in normally once more — Omniscio re-sends the verification mail whenever an unverified address tries to sign in.
Password rules
| When | Minimum |
|---|---|
| Creating an account, or setting a password | 12 characters |
| Signing in with a password you already have | whatever it already is |
The floors differ on purpose. Raising the minimum for new passwords must never lock out someone whose existing password is shorter — their password still works.
Related
- Deleting your account / starting from scratch
- User Management — roles, invites, and workspaces once you are in
Last verified 2026-11-11