Login Problem

Most login tickets resolve when the correct account is identified, a fresh temporary password is issued, or a 2FA configuration is corrected.

• Confirm which account and application is actually locked out before requesting a reset — misidentifying the system (e.g., email vs. a separate deposits app) is a common cause of failed first attempts.
• Attempt self-service password recovery first: visit the app's login page and use the "Forgot password" or account-recovery flow with your work email address. This works for apps like Adobe without needing admin involvement.
• Request a temporary password (admin only) if self-service recovery fails. When the admin sends one, use it immediately — temporary passwords can expire — and change it to a personal password as soon as you're in.
• Check 2FA settings on a new device or after a phone number change: if verification codes are going to an old phone number, the 2FA enrollment must be updated. Try available backup recovery options (backup codes, alternate email) before filing a ticket.
• Escalate a 2FA mismatch to the admin team (admin only) if 2FA appears disabled on your account despite your role requiring it, or if all standard recovery options fail. An admin with Google Workspace access may need to inspect your Organizational Unit settings.
• As a last resort, delete and recreate the account (admin only): if the account cannot be recovered — especially after a phone number change breaks 2FA with no backup method — the admin may need to delete the account and provision a new one.

If none of these solve it, file a ticket and include: the specific application name, the exact error message or screenshot, whether you recently changed devices or phone numbers, and whether this is a new account or a rehire/returning-user scenario.