Team and access. Give each employee a login and decide who can take payments.
Sign-in security for you and everyone on your team.
Every login to MeridianOS™ can use a passkey with Face ID or Touch ID, or a code from an authenticator app. Repeated wrong passwords trigger a lockout, and changing a password signs that account out everywhere else.
Passkeys built in. Sign in with Face ID or Touch ID on your device.
Lockout after failed tries. Too many wrong passwords pauses sign-in for that username.
App lock. The iPhone app asks for Face ID after five minutes away.
Access ends fast. Remove someone's access and their app signs out within minutes.
Passkeys and two-factor on every account.
A new password must pass a live checklist of 12 characters, an uppercase letter, a number and a special character. Add a second step with codes from an authenticator app, or add passkeys that sign you in with Face ID or Touch ID. A passkey also counts as the second step.
- Eight wrong tries on a username within 15 minutes trigger a lockout
- Twenty failed tries from one network trigger a lockout too
- Turning off two-factor requires a current code from the app
- Name each passkey and see when it was added and last used
When someone is locked out or moves on.
If an employee loses their phone, an admin can reset their two-factor or remove their passkeys from the employee page. Remove access ends their login and leaves their jobs and history in place. Change a password or remove access, and every session that person has ends at once.
- The employee page shows whether two-factor is on and how many passkeys exist
- The MeridianOS™ app notices removed access within minutes and signs out
Already handled. The details that usually get missed are built in.
Password rules hold everywhere
Password rules are checked by MeridianOS™ when a password is saved, as well as in the live checklist. A weak password cannot slip through another way.
Guessing hits a wall fast
Failed sign-ins are counted per username and per network over 15 minutes. Someone guessing at one account, or at many from one place, gets locked out with a clear wait time.
Sessions are stored safely
Sessions last seven days on the web and are stored only in hashed form. In the app, sign-in details stay in the phone's secure storage for that device only.
The app locks itself
The MeridianOS™ app asks for Face ID after five minutes away and on every fresh launch. It is on by default, and the lock screen offers Sign out too.
Keep exploring.
iPhone. Your schedule, customers, invoices, and payments, wherever you are.
Employee portal. Each employee sees their own schedule and what they have earned this pay period.
Questions and answers
Do my employees get the same protection?
Yes. Employees use the same sign-in, and they can add two-factor codes or passkeys from their own Security page. Lockouts and password rules apply to them too.
Is two-factor required?
No. It is optional, and anyone who signs in with only a password is offered a Secure your account prompt to add a passkey or an authenticator app. They can choose Not now and add it later.
What if an employee loses the phone with their passkey or codes?
An admin can reset their two-factor or remove their passkeys from the employee page. They then sign in with their password and set up a new second step.
How long does a sign-in last?
Seven days on the web. The app stays signed in while you use it and locks with Face ID after five minutes away.
See how MeridianOS™ protects your own team's logins.
We will walk you through passkeys and two-factor on a live system. Tell us what you do and we will reply within the hour.