Signing in and password reset

Getting back into your account, and what to do when you cannot.

/loginAnyone with an account

Signing in

Your email address and your password. That is the whole form.

Where you land afterwards depends on your role. Almost everyone arrives at their brands list. A platform administrator arrives at the platform dashboard instead. If you followed a link to a specific page and were asked to sign in first, you land on that page.

Invalid email or password means one of the two is wrong, and Sparkia deliberately does not say which. That is on purpose: telling you which half was right would help someone guessing at your account.

The Google and GitHub buttons are visible but inactive. Email and password is the only way in today.

The form, part by part

The sign-in form. Hover a number to read what each part does.

sparkia.io/login

Welcome back

Enter your credentials to access your account

amira@maisonlumen.fr

PasswordForgot password?

••••••••••••

or continue with

Google

GitHub

Don't have an account? Sign up for free

Resetting a forgotten password

Forgot password? beside the password label starts a four-step flow that all happens on one page. You do not need anyone's help and you do not lose your account.

1Enter the email address on your account and choose Send code. A six-digit code is sent to it.
2Type the code. It verifies itself the moment you enter the sixth digit, so there is no button to press.
3Choose a new password. Same strength rules as signing up, and the same Generate a strong password shortcut.
4You are told the password is updated. Choose Sign in and use the new one.

A code lasts fifteen minutes. A live countdown under the boxes tells you how long is left. Once it runs out, Send a new code gets another.

Too many wrong attempts locks that code, not your account. Request a new code and continue.

Finishing a reset signs you out everywhere else. Your phone, your other browser, your colleague's machine if you ever signed in on it. That is the point: if someone else knew the old password, they no longer have a way in.

When the code does not arrive

The reset page tells you where the code went, and in some environments that is not your inbox. Read the notice above the boxes: if it says the code is printed to the server terminal, email is not configured on that deployment and whoever runs it has to read the code out to you.

If the notice is not there, the code is a normal email. Check the address you typed, check your spam folder, and use Use a different email if you got the address wrong.

Nothing in the reset flow reveals whether an account exists at an address. A code is reported as sent either way, so a wrong address fails silently rather than telling you the account is not there.

Worth knowing

There is nothing to confirm by email when you sign up. Only the password reset uses a code. If you are waiting for a confirmation email that never arrives, you are not blocked: just sign in.

A code can expire between verifying it and setting the password. If it does, the flow drops you back to the code step and says so rather than failing quietly.