For legal professionals utilizing the Neos case management platform by Assembly Software, the login portal is the gateway to firm-wide productivity. As a cloud-based solution hosted on Microsoft Azure, Neos requires a specific authentication flow that differs from standard web applications. This guide provides a detailed breakdown of how to navigate the Neos login process, configure secure access, and troubleshoot technical barriers that may prevent entry to the system.

Primary Login Access for Neos Users

The official entry point for the Neos web application is managed through a secure cloud URL provided by Assembly Software. Unlike local installations of legacy software such as Needles, Neos operates entirely within a web browser environment. To access the platform, users must have three distinct pieces of information: a verified email address (username), a secure password, and a unique Company ID.

The Significance of the Company ID

The Company ID is a critical identifier that directs the authentication request to the correct firm database within the Neos multi-tenant environment. This ID is typically assigned during the firm's initial onboarding process. If a user enters the correct username and password but fails to provide the precise Company ID, the system will deny access as it cannot route the credentials to the appropriate organizational bucket. IT administrators usually distribute this ID to staff during their first week, and it remains constant for the life of the firm’s subscription.

Authentication Methods and Single Sign-On

Neos leverages modern enterprise security protocols to protect sensitive litigation data and client information. Most modern law firms opt for an integrated approach rather than relying on isolated credentials.

Microsoft 365 Integration (SSO)

Since Neos is built on the Microsoft Azure backbone, it offers deep integration with Microsoft 365. Many firms utilize Single Sign-On (SSO), which allows staff to log in using their existing Microsoft credentials. This reduces password fatigue and enhances security by centralizing identity management. When the "Sign in with Microsoft" option is selected, Neos redirects the request to Microsoft’s authentication servers. Once the user successfully authenticates there, a secure token is passed back to Neos, granting access without the need for a separate Neos-specific password.

Multi-Factor Authentication (MFA) Requirements

Security compliance in the legal industry, particularly regarding SOC 2 Type II standards, necessitates the use of Multi-Factor Authentication (MFA) or Two-Factor Authentication (2FA). Neos enforces this to ensure that even if a password is compromised, unauthorized actors cannot access the firm's case files.

Upon entering credentials, users are typically prompted to enter a code generated by an authenticator app (such as Microsoft Authenticator or Google Authenticator) or received via SMS. For firms using Microsoft SSO, the MFA settings are governed by the firm’s Entra ID (formerly Azure Active Directory) policies.

Optimizing the Browser Environment for Neos

Because Neos is a sophisticated SaaS (Software as a Service) platform with heavy data interactions, the choice of web browser and its configuration can significantly impact the login experience.

Recommended Browsers

  • Google Chrome: Generally considered the optimal choice for Neos due to its high-performance V8 engine and compatibility with the Neos Chrome Extension.
  • Microsoft Edge: As a Chromium-based browser, Edge offers excellent performance and seamless integration with the Microsoft 365 ecosystem, making it a preferred choice for many legal IT departments.

Cache and Cookie Management

A common cause of login "loops"—where the page refreshes back to the login screen after entering credentials—is corrupted browser cache or expired cookies. Neos stores session tokens in the browser to maintain the connection. If these tokens become desynchronized with the server, the login attempt will fail. Regularly clearing the browser cache specifically for the Neos domain, or using an Incognito/InPrivate window, can determine if a login issue is browser-related.

Pop-up Blockers and Permissions

Certain features within Neos, including document generation wizards and third-party integrations like DocuSign, may trigger pop-ups during or immediately after the login process. Users must ensure that the Neos URL is added to the "Allow" list in the browser's pop-up and redirect settings. Furthermore, ensuring that JavaScript and cookies are enabled is mandatory for the Neos interface to render correctly.

Troubleshooting Common Login Errors

Even with the correct credentials, technical hurdles can arise. Understanding the specific error messages can expedite a resolution.

"Invalid Credentials" or "Authentication Failed"

This is the most frequent error and is usually the result of a typo in the username, password, or Company ID. It is important to remember that passwords in Neos are case-sensitive. If the error persists after three attempts, it is advisable to stop to avoid a temporary account lockout.

Account Lockout Scenarios

To prevent brute-force attacks, Assembly Software implements a lockout policy. If a user exceeds the allowed number of failed attempts, the account will be disabled for a specific duration (often 15 to 30 minutes) or until an administrator manually resets the status in the Staff Management section of Neos.

2FA Verification Failures

If the 2FA code is rejected, ensure that the time on the mobile device generating the code is synchronized with the actual time. Authenticator apps rely on Time-based One-Time Passwords (TOTP). If the phone's clock is off by even a minute, the generated code will be invalid. If a user loses access to their 2FA device, a firm administrator must reset their MFA settings within the Neos user profile.

The "White Screen" After Login

A blank white screen after a successful login often indicates a network-level blockage or a failure to load the application's JavaScript assets. This can occur in firms with overly restrictive firewalls or SSL inspection tools. IT staff should ensure that all necessary Neos and Azure endpoints are whitelisted within the firm’s network security appliance.

Administering User Access and Permissions

For firm administrators and IT managers, managing the login lifecycle is a core responsibility. This involves more than just creating a username; it requires configuring the appropriate security groups and permissions.

Creating New Staff Profiles

When a new employee joins the firm, the administrator must create a staff profile and assign a license. The email address used in this profile serves as the login username. It is vital that this email matches the user’s professional email, especially if SSO is intended.

Disabling Access for Terminated Employees

In the legal field, immediate revocation of access is a security necessity during employee offboarding. By disabling the staff profile in Neos, the administrator instantly kills any active sessions and prevents further logins. If SSO is used, disabling the user’s Microsoft 365 account provides an additional layer of immediate protection.

Managing Permissions and Roles

Neos allows for granular control over what a user can see and do after they log in. Permissions can be restricted based on case types, financial data, or administrative tools. If a user logs in but cannot see their assigned cases, the issue is likely a permission setting rather than a login failure.

Platform Status and External Factors

Occasionally, login issues are not localized to the user or the firm but are the result of a broader service disruption.

Checking the Neos Status Page

Assembly Software maintains a dedicated status page that monitors the health of the Neos platform, including the login service, the Neo SAI (AI features), and document storage. Before spending hours troubleshooting a local machine, users or IT staff should check the status page to see if there is a known outage.

Azure Service Health

Since Neos resides on Microsoft Azure, regional outages at Microsoft data centers can impact accessibility. While rare, these disruptions can affect authentication services globally or regionally. Modern cloud architectures are designed with high availability, but during major internet infrastructure events, some latency or intermittent login failures may occur.

Advanced Access: API and Technical Integrations

For firms using advanced automation tools or custom reporting via services like Supergood, the login process happens via API calls rather than a graphical user interface.

Programmatic Authentication

The Neos API requires a different set of headers and authentication tokens. Developers must programmatically pass the username, password, and Company ID to the authentication endpoint. These systems handle the 2FA challenge through secure handshakes. If a firm’s API integration fails while the web login works, the issue usually lies in an expired API token or a change in the firm’s Azure security policies that the integration has not yet accounted for.

Integration with Outlook and Word

The Neos Add-ins for Microsoft Outlook and Word require their own login session. Users often find that they are logged into the web application but the Outlook side-panel asks for credentials. This is because the Add-in operates as a separate mini-application. Ensuring that the browser used by the Add-in (often a hidden instance of Edge) has the same permissions and cleared cache as the main browser can resolve these discrepancies.

Best Practices for Secure Access

Maintaining a secure login environment is a shared responsibility between the software provider and the law firm.

  1. Unique Credentials: Never share Company IDs or passwords across staff members.
  2. Regular Password Rotations: If not using SSO, enforce a policy for regular password changes.
  3. Audit Logs: Firm administrators should periodically review login audit logs to identify any suspicious activity, such as logins from unexpected geographic locations.
  4. Device Security: Ensure that all devices used to log into Neos have active antivirus protection and the latest operating system updates.

Summary

The Neos login process is the foundation of a firm’s digital workflow. By understanding the tripartite requirement of Username, Password, and Company ID, and by embracing the security of Microsoft SSO and MFA, legal teams can ensure consistent access to their critical case data. While technical glitches such as cache conflicts or 2FA desynchronization can occur, most issues are easily resolvable through standard browser maintenance or administrative adjustments. Staying informed via the official status page and utilizing the resources in the Neos Academy can further empower users to maintain a seamless and productive environment.

Frequently Asked Questions

How do I find my Neos Company ID?

The Company ID is typically provided during your initial setup. If you do not have it, contact your firm’s Neos administrator or IT department. It is a unique string used to identify your specific firm's database.

Can I log into Neos from my mobile phone?

Neos is a web-based application optimized for desktop browsers. While you can technically log in via a mobile browser, the full functionality and interface are designed for a desktop experience. There is currently no native mobile app for Neos.

Why does Neos keep logging me out?

For security and HIPAA/SOC 2 compliance, Neos has an automatic timeout period for inactive sessions. Administrators can adjust these settings in the Firm Preferences section, but some level of auto-logout is necessary to protect sensitive data on unattended devices.

What should I do if I forget my Neos password?

On the main login screen, there is a "Forgot Password" link. Clicking this will prompt you to enter your email address and Company ID to receive a password reset link. If your firm uses Microsoft SSO, you must reset your password through your Microsoft 365 account settings instead.

Is the Neos login the same as the Needles login?

No. Neos is a cloud-native platform by Assembly Software. While it is the successor to the Needles on-premise software, the login credentials and infrastructure are entirely different. Users migrating from Needles to Neos will receive new credentials.

Does Neos support biometric login like FaceID?

Neos itself does not directly handle biometrics. However, if your firm uses Microsoft SSO and your device supports Windows Hello or biometric authentication for Microsoft 365, you can effectively use those methods to satisfy the primary authentication requirement.