Login Security Policy: Password Rules, 2FA, and SSO
Paminga's Login Security Policy gives admins one place to set password complexity rules, length minimums, special character requirements, two-factor authentication enforcement, and SSO with Okta or Google.
Security policy lives in a setting most teams configure once and forget — which is exactly why it should be easy to get right the first time. Here's what's there.
Password Defaults
Out of the box, every Paminga password must contain:
- At least 1 lowercase letter
- At least 1 uppercase letter
- At least 1 number
That's the floor. The next two settings let you raise it.
Require Special Characters
When enabled, passwords must also contain at least one of: @ $ ! % * # ? &
Recommended for any team that handles customer data — which is to say, every Paminga team.
Minimum Password Length
Set anywhere between 6 and 16 characters. Most security guidance lands at 12+ — pick what fits your org.
Two-Factor Authentication
Enable Require Two-Factor Authentication and every user must configure and use 2FA to access Paminga.
This is the highest-leverage security toggle in the system. Stolen credentials are the #1 breach vector across SaaS. 2FA stops nearly all of them.
❌ Don't leave 2FA optional in 2025.
✅ Do require it for every user. The 30 seconds of setup is worth the risk reduction.
Okta SSO
Paminga supports SSO with Okta. The setup is short:
- An Okta admin adds the Paminga application to Okta
- Save the integration settings on the Login Security Policy page in Paminga
- Users log in with their Okta credentials
Once saved, you're set. Read more in my Okta SSO post.
Google SSO
Paminga supports SSO with Google with no setup required. Click Login with Google on the login page and follow the prompts.
Most teams with Google Workspace can stop reading there.
Why This Matters
The Login Security Policy is the configuration that determines how likely your Paminga account is to get compromised by a phishing campaign, a leaked password from another service, or a forgotten ex-employee whose credentials never got rotated.
The defaults are reasonable. The toggles take ten seconds. The risk reduction is real.
Get Started
- Open Account Settings → Login Security Policy
- Decide your password complexity floor — at minimum, set a 12+ character length and require special characters
- Require Two-Factor Authentication. Don't make this optional.
- If your team is on Okta or Google Workspace, configure SSO
Read the Login Security Policy docs to dig in.
