Signing in with Google
What Continue with Google does for a new account, and what it does for one you already have.
Continue with Google sits at the top of the sign-in page, above the email and password fields. It is the same account either way — Google is a way of proving who you are, not a separate kind of login. What it does next depends entirely on whether an account already exists for that address.
The flow
Four moves, three of them invisible. The whole sequence is a full-page redirect, so do not close the tab while it is running.
- 1
Choose Google
Sign in → Continue with GoogleThe register page offers the same thing under Sign up with Google. Both end in the same place; there is no separate Google account to create first.
- 2
Approve at Google
You leave Cooriroo entirely and consent on Google’s own page. Nothing about your Google password is ever seen by Cooriroo.
- 3
Come back
Google returns you to Cooriroo, which checks that the reply matches the request it sent, and only then establishes your session.
- 4
Land where you belong
Existing account, existing workspace. New account, the setup wizard. See below for how those two differ.
What happens the first time
The first time a particular Google account signs in, Cooriroo has to decide whether it belongs to somebody it already knows. There are exactly three answers, and they are worth understanding before you tell a colleague to "just use Google".
| If your email address… | What happens | Where you land |
|---|---|---|
| Has no Cooriroo account | A new admin account and a new empty workspace are created | The setup wizard |
| Has a verified Cooriroo account | Google is attached to that account | Your existing workspace |
| Has an unverified account | Sign-in is refused and the address owner is emailed | Back to the sign-in page |
The refusal in the third row is a security measure rather than a fault. An unverified account is one where nobody has yet proved they own the address, so attaching a Google identity to it would let whoever arrives first take over an address somebody else registered. Verify the account through the email you were sent, then Google will link to it cleanly.
Where you land afterwards
Sign-in does not always end at the dashboard. Four gates are checked in order, and the first one that applies wins:
- an unverified email address sends you to verification;
- an account provisioned with a temporary password sends you to set your own;
- an admin whose workspace has never been set up goes to the setup wizard;
- otherwise you land in the application your account type belongs to.
An account created through Google skips the first gate outright: Google only hands over addresses it has verified, and Cooriroo rejects the sign-in if it does not, so there is nothing left to confirm.
When sign-in fails
Reading the banner on the sign-in page
“Sign-in was interrupted. Please try again.”
The reply from Google arrived without something the request had set up.
Almost always harmless: a stale tab, a link opened twice, a back button pressed mid-flow, or cookies cleared between leaving and returning. Start again from the sign-in page rather than reloading the returned URL.
“We couldn’t complete sign-in with Google.”
The exchange with Google itself did not succeed.
Try once more. If it persists, sign in with email and password instead and raise it through Platform → Support — this one is not something you can fix from your side.
“Sign-in completed but session didn’t start.”
Cooriroo accepted the identity but no session was present on the way back.
Usually a browser that is blocking cookies for the site. Allow cookies for Cooriroo, or try a normal window if you are in a private one.
Google succeeds but you are returned to sign-in with no obvious reason
An unverified local account exists under the same address.
The message stays deliberately vague, because a precise one would tell an attacker which addresses have accounts. Finish verifying that account — or activate the invitation you were sent — and try Google again.
You signed in and the workspace is empty
A new workspace was created because no account matched your address.
Nothing has been lost. Ask whoever runs your existing workspace to invite the exact address you used, activate that invitation, and sign in with Google again — it will attach to the invited account from then on.
- Inviting your teamThe invitation flow Google sign-in attaches to, and how to resend one.
- Who does whatWhich application each account type signs in to, and why.
- Your first 15 minutesWhat to do once you are through the door and looking at an empty board.
- JWT vs API keyHow sessions differ from the credentials an integration uses.