Kiket docsSign-in and accounts
Email and password, Google and GitHub OAuth, account linking, and how this differs from integration OAuth.
The web app signs you in with email and password or with Google or GitHub as an identity provider. API automation uses API Keys under Settings → API Keys (see API & SDKs).
Platform sign-in is separate from integration OAuth: connecting GitHub to clone repos uses different OAuth scopes and callbacks than “Sign in with GitHub.” Evidence adapters (GitHub, Jira, ServiceNow, webhooks) use installation-scoped API keys and ingress routes — not workspace sign-in.
Email and password
Create an account with your email, name, and password. Passwords are hashed securely on the server.
Google and GitHub (platform OAuth)
On the sign-in screen, use Continue with Google or Continue with GitHub. The platform requests only what it needs to identify you (for example OpenID email / profile for Google, and read:user / user:email for GitHub). After you approve the provider, the app finishes sign-in in the browser and stores session tokens the same way as for password login.
If your user belongs to more than one organization, you will see the same organization picker as with email login.
Linking providers to an existing account
You can connect Google or GitHub from Settings → Security → Connected accounts while signed in. Provider emails do not need to match your Kiket account email — each provider is linked explicitly to your user.
If you sign in with a provider instead, and an account already exists with the same verified email, that OAuth identity is linked automatically. You will not get a duplicate account.
If the provider does not confirm the email as verified during sign-in, automatic linking is blocked and you will see an explanatory error — sign in with your password, connect the provider from Settings, or ensure the provider account uses a verified email.
You must keep at least one sign-in method (password or a connected provider). OAuth-only accounts can set a password via Forgot password on the sign-in screen when email delivery is configured.
Password reset and notification email require Mailjet (or equivalent platform configuration) on self-managed deployments. Operators set MAILJET_* secrets and APP_URL; see Self-host.
Private and self-managed deployments
If your organization runs Kiket in its own environment, your administrators enable Google or GitHub sign-in in the platform configuration. You use the same Continue with Google and Continue with GitHub buttons as in the hosted product; end users do not register OAuth apps or manage credentials.
Deployment, callbacks, and secrets are covered in the Self-host guide for operators.