PanicStation.org
UK USA
uk Technology & digital loss

What to do if…
you lose access to a shared work account or workspace unexpectedly

Produced and maintained by PanicStation.org Published: Last reviewed: Editorial policy UK guide

Short answer

Stop trying random fixes, capture what you are seeing, and contact your IT/helpdesk and manager with a clear request to confirm what changed and restore the access you need.

Do not do these things

  • Do not try to work around access controls by using someone else’s login, personal accounts, VPN tricks, or exporting restricted files.
  • Do not repeatedly push login or MFA attempts; this can trigger further lockouts and may look suspicious.
  • Do not message wide groups accusing someone of misconduct; keep first messages factual and private.
  • Do not install unapproved apps or browser extensions to get back in.
  • Do not delete local files, emails, or chat history in a panic.
  • Do not move work files to personal storage unless your organisation’s policy clearly allows it.

What to do now

  1. Pause and record exactly what changed.
    Write down the time it started, the workspace or tool affected, the action that fails, and the exact error message. Include whether it is a full sign-in failure or missing access to particular files, folders, channels, boards, or projects. Take a screenshot if your organisation’s policy allows it.

  2. Separate sign-in problems from permission problems.
    If you cannot sign in at all, note whether the message mentions password, MFA, account disabled, licence removed, or contact admin. If you can sign in but cannot see specific shared work, this often points to a permission, group membership, licence, workspace, or project-access change.

  3. Open an urgent IT ticket or call the helpdesk.
    Use clear wording: “My role or access appears to have changed without warning. I have lost access to [workspace] needed for today’s work. Please confirm whether my account was disabled, downgraded, relicensed, suspended, or removed from a group, restore the required access, and tell me if this was a security action.” Ask for a ticket or reference number.

  4. Ask your manager to confirm the change in writing.
    Send a short message: “I have suddenly lost access to [workspace]. IT ticket [number] is open. Can you confirm whether my role or permissions were changed and what I should do next?” Keep it factual and avoid guessing why it happened.

  5. Treat possible compromise as a security issue.
    If you see MFA prompts you did not start, unfamiliar device or session notices, password reset messages you did not request, or alerts about sign-ins from places you do not recognise, report it to your IT or security contact as suspected account compromise. Ask them to check recent sign-ins, revoke active sessions or force sign-out if appropriate, and tell you the approved password reset and device-check process.

  6. If you were an admin or owner, ask for controlled recovery.
    Ask IT or security for the organisation’s administrator recovery route, sometimes called emergency admin recovery or break-glass access. Ask them to log any temporary access, ownership transfer, user restoration, licence change, or group membership change they make.

  7. Protect today’s work without moving restricted data.
    Make a short list of deliverables blocked by the access loss. Keep any local drafts only in approved storage on a managed device or approved drive. Tell the relevant project owner you are blocked pending IT restoration, using impact-based wording rather than blame.

  8. If this may be a role or employment change, keep it procedural.
    Ask for the change and its immediate impact on duties, access, reporting line, or work allocation in writing. You can consider speaking to a union representative, staff representative, or ACAS later, but the first step is to stabilise access and get confirmation.

What can wait

  • You do not need to decide today whether to challenge the role change formally.
  • You do not need to write a long explanation to colleagues or clients right now.
  • You do not need to clean up accounts, files, or chats in the moment.
  • You do not need to guess whether this is disciplinary, redundancy-related, a security safeguard, an admin mistake, or a licence issue.
  • You do not need to solve the whole employment or contract question before IT confirms what happened.

Important reassurance

Sudden access loss can happen because of reorganisations, licence changes, group-policy updates, security controls, account sync issues, or admin mistakes. The safest move is to slow down, record what you see, and route it through IT and your manager so it can be checked and corrected cleanly.

Scope note

These are first steps to stabilise the situation, avoid policy breaches, and create a clear record. Later decisions about employment rights, grievances, contract changes, security investigation, or data requests may need specialist help.

Important note

This guide provides general first-step information only. It is not legal, HR, cybersecurity, employment, financial, therapeutic, or other professional advice. Follow your organisation’s policies and use official IT, security, and management channels where possible.

Additional Resources

Closely connected guides that may be useful during the same situation or its immediate aftermath.

About this guide

This guide was produced and is maintained by PanicStation.org using its published editorial process. Official and specialist sources are checked where relevant, and AI-assisted tools may be used for drafting, organisation, and consistency checks. The site operator remains responsible for publication, revision, and removal decisions.

Support us