Overview
This page explains how signing in to Legora works and points you to the right article for your task. Your organization decides how its members sign in. Members sign in with single sign-on (SSO) through the organization’s identity provider, with an email address and password, or with either. Organizations can also require two-factor authentication for password sign-ins. Legora is moving organizations from regional authentication to Legora’s global authentication. New organizations start on Legora’s global authentication. On regional authentication, Legora support manages sign-in settings. On Legora’s global authentication, Admins manage them themselves.Which sign-in system does your organization use?
Some steps depend on the sign-in system your organization uses. You can tell from the address you sign in at.For everyone
These articles help you sign in and fix sign-in problems:- Why can I not log in to Legora?: Fixes for common sign-in errors, password resets, and SSO problems.
- How do I change the way I log in to Legora?: Who decides how you sign in.
For Admins and IT
These articles cover authentication settings and identity provider setup:- How do I manage authentication for my organization?: Sign-in methods, two-factor authentication, session timeout, IP restrictions, and SSO connections.
- Integration Overview - Entra ID Single Sign-on: Set up SSO with Microsoft Entra ID.
- SAML SSO Integration Guide: Set up SSO with a SAML 2.0 identity provider.
- Directory Sync: Provision members and groups from Microsoft Entra ID or Okta.
- Enabling the Azure AD integration for your organization: Sync Entra ID group membership into Legora groups.
- Legora network and domain requirements: Domains to allow on your network, including sign-in domains.
Moving to Legora’s global authentication
These articles cover the move from regional authentication to Legora’s global authentication:- IT Admin guide: Legora’s global authentication: The full migration task list, from identity provider updates to cutover.
- Migration action required: callback URLs and allowlist updates: Callback URLs and domains to add before cutover.