What people keep running into with access management
Complaints tagged access management, each raised by more than one person. One-off posts are not included.
8 recurring problems · 41 people · 10 forums we read
Raised more than once
Most people first.
- 15Why am I getting locked out of my account when using the correct password?Intermittent platform lockouts can occur following authentication updates like passkey rollouts, blocking users and admins from signing in for up to a few hours despite entering correct credentials. This unexpected lockout prevents access to organizational accounts and disrupts workflows without an immediate fix from changing passwords.
- 8Why are our Salesforce accounts getting blocked for high-risk proxies?Legitimate network connections are being incorrectly flagged as high-risk anonymizing proxies like TOR or Mullvad, causing administrator accounts to be repeatedly blocked. This leaves organizations locked out of their accounts for months without a clear way to prevent the behavior.
- 5How to catch all account dependencies during user offboardingStandard offboarding catches email and licenses, but misses hidden dependencies like Power Apps, custom flows, and SharePoint ownership tied to the departing account. This leaves administrators manually digging through every admin center to prevent broken workflows and orphaned assets.
- 5Tracking down unmanaged SaaS accounts when an employee leavesCentral SSO cuts off many access points, but employees often leave behind a messy tail of separate credentials, service portals, API tokens, and rogue accounts created without lifecycle integration. This leaves sysadmins hunting down unmanaged services by hand instead of fully securing offboarding in one place.
- 3Why do former employees still have active logins?IT departments often lack timely communication from HR regarding departure dates, leaving accounts active long after employees leave. This breakdown in the offboarding process leaves systems exposed to former staff retaining access for months or even years.
- 2Why does Salesforce require another login after Okta 2FA?Salesforce does not recognize Okta's 2FA as sufficient, forcing users to jump through multiple verification processes just to gain access. This creates an awful "MFA all the time" workflow that puts up a barrier to actually accessing the system. Ultimately, these extra security hoops make it even harder to get sales teams to use the tool.
- 2Why do software updates silently change how features work?Software updates often change long-standing default behaviors and workflows without warning, causing users to miss critical changes like modified copy dates or security settings. These silent shifts break established habits and lead to costly mistakes, such as overdue receivables or compromised account security.
- 2Logged out immediately after logging inAuthentication systems repeatedly clear the active session within seconds of signing in, failing to persist user credentials across initial redirects. This forces people into an endless login loop, blocking them from accessing the application entirely.
Comes up alongside
Topics that keep appearing on the same problems — not topics with similar names.