Account access and recovery

CogLake shows only the sign-in methods available for your installation. Managed SaaS can offer verified email accounts, Google sign-in and trial registration. Dedicated and On-Prem installations use administrator invitations or the organization's identity provider rather than public registration.

Join the correct organization

Registering creates a new organization; it does not join an existing company's workspace. Use an invitation from that company when you should become a member. An existing CogLake identity can accept another membership without creating a second password.

Verify a new account

1. 1Create the account
2. 2Confirm your email
3. 3Set up MFA if offered
4. 4Complete workspace setup

Enter the confirmation code from the latest email on the verification page, or use the verification link if offered. You can paste a complete code into the grouped input. Request a new message if the code expired; do not keep retrying an old one.

A successful verification can sign you in directly when the signup session can be continued safely. If the link was opened in another browser or the session expired, sign in normally. CogLake can then offer two-factor setup; Skip for now is available only when the current flow permits it.

Personal two-factor authentication

For supported local SaaS accounts, open My settings → Sign-in & security.

1. Choose the option to set up two-factor authentication.
2. Confirm your password if requested.
3. Add the displayed setup information to a trusted authenticator app.
4. Enter the current authenticator code to complete setup.
5. Save the recovery codes somewhere safe, separate from the device used for authentication.

Never send the setup secret, QR code or recovery codes to support. An authenticator code is different from the email verification code.

At later sign-in, enter the authenticator code or an unused recovery code through the offered recovery option. Check the device clock if fresh codes repeatedly fail. Do not disable a required organizational MFA policy to work around a login problem.

Lost device or changing MFA

Use an unused recovery code when offered. After regaining access, review the factor and replace it as appropriate. Disabling personal MFA requires the verification requested by the settings. If both the device and recovery codes are lost, contact the responsible administrator/support; do not create a second company to bypass access controls.

For provider-managed accounts, MFA and recovery belong to the identity provider. See enterprise authentication.

Password reset and sessions

Choose Forgot password? where available. The same confirmation is shown whether or not an account exists. Use the newest email to choose a password meeting the displayed requirements. On installations without email recovery, contact the administrator.

Review active sessions and revoke sessions you no longer recognize where the security settings offer this. Signing out of one browser is different from revoking other sessions.

Google sign-in

Choose Continue with Google and select the intended account. Your address must be verified and may be subject to approved-domain rules. Google sign-in for CogLake is separate from connecting a Google Drive source.

For wrong-organization, invitation or permission problems, see access troubleshooting.