Skip to main content
All CollectionsContacting supportTroubleshooting common issues
I can't create an account, log in or access Legatics
I can't create an account, log in or access Legatics

Resolve issues accessing Legatics, including forgotten passwords, incorrect URLs, and two-factor authentication problems

Updated this week

Access issues can prevent you from using Legatics effectively, but they’re often easy to resolve. Whether a URL is blocked by your organization or you’re encountering connectivity problems, this section outlines steps to troubleshoot and ensure seamless access to the platform.

Heads-up: Legatics can't invite you to matters


You don't have an account or aren't allowed to create one

Only certain people can create accounts. Check that you're allowed to create an account on the instance you're logging into.


You haven't been added to your SSO group

If you receive an AADSTS50105 error (that looks like the one below), then you'll need to contact your internal IT team to get access to Legatics. The issue is caused by your SSO system. Your SSO administrator needs to add you to the group that can access Legatics.

AADSTS50105: Your administrator has configured the application Legatics 2 (Europe) to block users unless they are specifically granted ('assigned') access to the application. The signed in user '{email}' is blocked because they are not a direct member of a group with access, nor had access directly assigned by an administrator. Please contact your administrator to assign access to this application.


Your password is incorrect

Try resetting your password, it may solve your issues.


You're logging into the wrong instance

Legatics has multiple instances. Each instance is separate - matters and users aren't shared between instances. Make sure you've logged into the instance that hosts the matter.


You're using an unsupported browser

We only support certain browsers. Make sure you're using the right one!


Legatics is blocked by your organization

Contact your IT team to ensure the base URL of the instance hosting the matter is added to your organization's whitelist. If the issue persists, request your IT team to check firewall or proxy settings that may block access to the platform.

Tip: You can test if this is the issue. Simply try log into Legatics from your phone (on mobile internet). If you can log in, then it's definitely something on your end.

Did this answer your question?