How to sign in with SSO (Microsoft Entra ID) or email/password, plus troubleshooting
Cloosphere supports both SSO (Single Sign-On) and email/password sign-in. In enterprise environments, SSO based on Microsoft Entra ID (Azure AD) is recommended.
The available sign-in methods depend on admin configuration. If a method isn’t shown on the sign-in screen, contact your IT admin.
OAuth sign-in options (Microsoft, Google, GitHub, etc.) only appear on the sign-in screen if the admin has configured the corresponding provider via environment variables.
The sign-in screen. Which SSO buttons appear depends on the providers your admin configured
SSO (Microsoft)
Email / Password
LDAP
The recommended sign-in method for enterprise environments using Microsoft Entra ID (Azure AD). Sign in with your corporate account — no separate account creation needed.
If your admin has not allowed automatic account creation on first SSO sign-in, only users the admin created in advance can sign in with SSO. Authenticating without an existing account shows an access-permission error, so ask your IT admin to register your account.
1
Open Cloosphere
Enter the Cloosphere URL provided by your admin in the browser address bar.
2
Click the SSO button
Click the “Continue with Microsoft” button at the bottom of the sign-in screen.If your admin also configured the Google provider, a “Continue with Google” button appears above it. The rest of the flow is identical — you just authenticate with a Google account instead of Microsoft.
3
Authenticate with Microsoft
You’ll be redirected to the Microsoft sign-in page. Enter your corporate email and password, or pick an account that’s already signed in to the browser.
If you’re already signed in to Microsoft 365, you’ll be authenticated automatically by selecting your account.
4
Land on the main screen
Once authenticated, you’ll be redirected to the Cloosphere main chat screen.
The main chat screen you land on after signing in
Benefits of SSO:
No separate account creation needed
Corporate password policies apply automatically
MFA and other corporate security policies carry over
Organization information syncs automatically
Sign in with email and password when SSO isn’t used.
1
Open Cloosphere
Enter the Cloosphere URL provided by your admin in the browser.
2
Enter email
Enter your registered email address in the Email field.
If your admin enabled email de-identification mode, this field appears as Account ID (placeholder Enter Your Account ID). In that case, enter the account ID issued by your admin instead of an email address.
3
Enter password
Enter your password in the Password field.
4
Click sign in
Click “Sign in” or press Enter.
Use this method when an LDAP directory service has been configured.
1
Open Cloosphere
Enter the Cloosphere URL provided by your admin in the browser.
2
Confirm LDAP mode
The sign-in screen displays in LDAP mode, with a Username field.If you see the email sign-in form instead, click “Continue with LDAP” at the bottom to switch. To go back from LDAP to email sign-in, click “Continue with Email”.
3
Enter credentials
Enter your LDAP username and password, then click “Authenticate”.
You can create your own account only if the admin has enabled new sign-ups. If it’s disabled, contact your IT admin to request an account.
When sign-up is allowed, click the “Sign up” link at the bottom of the sign-in screen to create an account.
1
Go to the sign-up page
At the bottom of the sign-in screen, click the “Sign up” button next to “Don’t have an account?”.
2
Enter your information
Fill in:
Name: Display name (real name recommended)
Email: Email address used for sign-in
Password: Password
Sign-up form: enter name, email, and password
3
Check password requirements
The password must meet all of the following:
Minimum 8 characters
At least 1 uppercase letter
At least 1 lowercase letter
At least 1 number
A password strength indicator shows compliance in real time as you type.
4
Complete account creation
Once all conditions are met, the “Create Account” button activates. Click it to create the account.
Depending on admin settings, your account may go into a pending state after creation. In that case, an admin must approve the account before you can sign in.
SSO appears on the sign-in screen only when an admin has configured an OAuth provider. If “Continue with Microsoft” is missing, ask your IT admin to set up OAuth (configured via environment variables).
I get an incorrect email or password error
Your email or password is wrong. The actual message is “The email or password provided is incorrect. Please check for typos and try logging in again.” Check:
Email typos (case-insensitive)
Caps Lock state
If you forgot your password, ask the admin to reset it (if you still know your current password, you can change it yourself under Settings → Account → Change Password after signing in)
I see an 'Account Activation Pending' screen after sign-up
When the admin requires approval after sign-up, sign-in itself succeeds, but if your account is in pending state you’ll see an Account Activation Pending screen right after entering (“Your account status is currently pending activation.”). An admin must approve your account, so contact your IT admin to activate it.On that screen, Check Again re-checks approval status and Sign Out lets you switch to another account. The responsible admin’s name and email are shown as well, unless the admin has turned contact display off.
Permission error after Microsoft sign-in
Occurs either because of a permission problem on the Microsoft Entra ID side, or because no matching account exists in Cloosphere. If Microsoft authentication itself succeeds but you see “You do not have permission to access this resource…”, your account does not yet exist in Cloosphere and SSO auto-signup is off. Ask your IT admin to verify:
Whether your account is registered in Cloosphere (or whether SSO auto-signup is allowed)
Cloosphere is registered as an app in Azure AD
Your user or group has app access permission
Required API permissions (User.Read, etc.) are consented
I get kicked back to the sign-in screen mid-task
In environments where the admin has set a session lifetime, your sign-in token expires and you are signed out automatically and returned to the sign-in screen with the message “Your session has expired. Please sign in again.” Signing back in usually returns you to the screen you were on; if expiry repeats on the same screen within a short window, you land on the main screen instead.
