Hi everyone,
We have news. Very. Exciting. News.
Single Sign-On (SSO) is now free for all properties 🎉
Peace of mind when it comes to security is priceless. Now, with Mews that’s literally true – because we’ve decided to make our premium security feature free to all Mews customers.
Phishing remains a real threat in hospitality and logins are often the easiest way in. SSO helps protect your team and guest data by reducing the risk of password-based attacks. Below, we’ll cover what it is and how to switch it on.
What SSO does
SSO lets your team sign in to Mews using your company login, so you don’t need separate Mews passwords. But it also offers your team a more frictionless sign-in experience.
-
One login: Access Mews through your existing company login.
-
Stronger protection: Reduce the risk of phishing and unauthorized access.
-
Faster, frictionless access: Staff log in and out easily across shifts and devices.
-
Simpler on/offboarding: New hires don’t need a Mews password and access is removed automatically when people leave.
Here's how to set it up:
How do I activate SSO?
Setup depends on whether you manage one property or multiple in Mews:
Single properties
-
Go to Security features > Single sign-on (SSO) and click Request
-
We’ll email you when it's approved (typically 2-3 business days)
-
Return to Security features, click Configure and follow the steps
Multi-property accounts
-
Go to Security features
-
Click Configure and follow the steps (no request needed)
For more a detailed walk-through with images, read the setup guide.
Can everyone use SSO?
All properties that use private email domains (e.g. email@yourhotel.com) and an Identity Provider (like Microsoft Azure, Google Workspace or Okta) can use SSO.
What happens if I already pay for SSO?
All SSO charges ended on 31 December 2025. This happened automatically, so you don’t need to do anything. You will no longer see any charges for SSO on your invoices.
Other questions? Check out all Single Sign-On FAQs here. Or drop your question in the comments below.
