Sign in at business.didit.me with SSO, a passkey, or email and password, and fix forgotten passwords, lockouts and the common missing-organization problem.
If you signed in successfully but your team's workflows and history aren't there, you're in a different organization from theirs - usually one you created, or you signed in with a different email than the one invited. Ask an owner to invite your email, then accept it from the organization menu at the top of the sidebar. The data isn't lost.
You sign in to Didit at business.didit.me with Google, Microsoft, GitHub or Apple, a passkey, your company's single sign-on, or an email and password. Most access problems come down to being in the wrong organization or a locked password, not lost data.
#Signed in, but your organization's data is missing
This is by far the most common access problem, and it isn't a bug.
When you first sign in, the console offers any invitation waiting for your email (Accept and open), even if you didn't use the invite link. With no invitation, it asks you to Create an organization. If you create one at that point, or sign in with a different email from the one your team invited, you end up in a separate, empty organization: your colleague's workflows, API keys, and verification history live in theirs, and you're looking at yours.
To fix it:
- Ask to be invited
Have an owner or admin of the correct organization invite your email under Settings → Members. See inviting team members and setting roles.
- Accept and switch
Open the organization menu at the top of the sidebar. The invitation shows there with Accept, and the same menu switches between every organization you belong to - one person can be in several.
- Clean up the duplicate (optional)
An empty organization you created by mistake does no harm. If you want it removed, contact support and they'll handle it.
If instead a page won't load, shows a server error, or history looks genuinely missing after you're confirmed in the right organization, that's not something you did. Contact support rather than trying to work around it.
#Forgot your password
Use the reset link on the login page and follow the instructions sent to your email. If you signed up with SSO, reset your password with your identity provider instead - there's no separate Didit password to recover.
#Too many failed attempts
Entering the wrong password several times in a row temporarily locks the account as a security measure. Wait before trying again, or use the reset link to set a new password rather than continuing to guess - each guess extends the lockout.
#Changing your login email
Your sign-in email can't be changed from the console: your profile shows it as permanent. Contact support to change it. Inviting a new address as a member and removing the old one also works, but it creates a separate account, which loses the old account's passkeys and personal settings.
#Switching from a social login to email and password
Where it's available (it's rolling out), Settings → Your account → Security → Sign-in methods lets you Set password and connect or disconnect Google, Microsoft, GitHub and Apple on the same account. Otherwise, the route is the same as changing your email: contact support, or have the target address invited as a member with your role and then remove the old identity.
#Passkeys and second factors
If you're stuck behind an extra sign-in step - a passkey that no longer works, a lost second factor, a new phone - contact support so they can verify who you are and restore access. Don't keep retrying; repeated failures extend the lockout.
Asked for a passkey you never created, or one that fails. Passkeys are per device, so a new phone or a wiped browser won't have yours. Support can reset the passkeys on the account, but for security they first send you an identity verification link (a short Didit session with your ID and a selfie). Complete it, reply on the same ticket, and they clear the passkeys so you can sign in with your email and password or SSO again and register a new one under Settings → Security in your account, under Two-factor authentication.
Lost the authenticator app (2FA) with your phone. Use one of your recovery codes: you got 5 when you turned on the authenticator app, and the sign-in screen offers Use a recovery code instead. Each code works once; once you're in, create a fresh set under Settings → Your account → Security → Recovery codes → Create new codes. If you have no codes left and can't restore the app from its own backup, contact support: after the same identity verification they disable the second factor so you can enrol a new one.
Some actions are deliberately gated behind an extra confirmation even after you're signed in. That's intentional for sensitive changes, not a fault.
#"Too many attempts" when signing up
If sign-up answers Too many attempts. Wait a moment before you try again., nothing is wrong with your details. This is the sign-up rate limit, and it is tied to the public IP address you're connecting from, not to the email address or the browser - which is why an incognito window and a different email make no difference. It trips after a few attempts from the same network in a short window, and an office or shared network (or a VPN) can hit it even on your first try because colleagues share the address.
Two things get you through:
- Sign up from a different network. The easiest is your phone on mobile data with Wi-Fi off, at business.didit.me. That gives you a fresh address and the registration goes through immediately.
- Or wait, without retrying. The limit clears on its own after a while. Each new attempt can restart the countdown, so if you've been retrying every few minutes it never actually elapses.
If neither works, tell support the public IP you're signing up from and they'll clear the limit for it. Once you're in, pick the mailbox you personally read as the account owner: that's where API keys, billing notices and security alerts land.
#Signed in through GitHub or Google and landed in the wrong account
A social login is tied to the email that provider reports. If your GitHub account is linked to a different email than the one your organization invited, signing in with GitHub signs you in as a different person, with no invitation waiting - and if you create an organization from there, it's a separate, empty one: the classic missing-organization problem above. Changing the email inside GitHub afterwards produces yet another new account rather than merging. The fix is the invite route: have the owner invite the address you actually want to use, then contact support to remove any empty organizations and, if needed, transfer ownership after they've verified you.
#Organizations using SSO
If your organization has SSO configured, sign in through your identity provider rather than a password. If password sign-in is unexpectedly blocked, that's usually an SSO policy your own admin controls - check with them before contacting support.
#Getting help when you can't sign in
Support will ask for something that identifies your organization. If you can't reach the console at all, send the email address you sign in with and, if you know it, your organization ID from a previous URL. Asking someone to send a console screenshot when the problem is that they can't reach the console isn't useful - say plainly that you're locked out and they'll take it from there.
Still stuck? Talk to a human.
Include your organization ID and the session ID you are asking about.