Sign-in and authentication - Legora

Overview

This page explains how signing in to Legora works and points you to the right article for your task. Your organisation decides how its members sign in. Members sign in with single sign-on (SSO) through the organisation’s identity provider, with an email address and password, or with either. Organisations can also require two-factor authentication for password sign-ins. Legora is moving organisations from regional authentication to Legora’s global authentication. New organisations start on Legora’s global authentication. On regional authentication, Legora support manages sign-in settings. On Legora’s global authentication, Admins manage them themselves. Some steps depend on the sign-in system your organisation uses. You can tell from the address you sign in at.

	Regional authentication	Legora’s global authentication
Sign-in address	A regional URL: `app.eu.legora.com`, `app.us.legora.com`, `app.ap.legora.com`, or `app.au.legora.com`	app.legora.com, then your organisation’s dedicated URL, such as `acme.app.legora.com`
Password reset	A reset link by email	A one-time code by email
Minimum password length	12 characters	15 characters
Too many wrong passwords	Sign-in shows Account Blocked	Sign-in pauses for a short time
Who manages SSO, two-factor authentication, and IP restrictions	Legora support	Admins, in Settings > Authentication
Mobile app region	Your region	Global

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 organisation?: 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 organisation: 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

This article covers 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.

​Overview

​Which sign-in system does your organisation use?

​For everyone

​For Admins and IT

​Moving to Legora’s global authentication

Overview

Which sign-in system does your organisation use?

For everyone

For Admins and IT

Moving to Legora’s global authentication