What to do if…
you lose access to a shared workspace because your role was changed without warning
Short answer
Treat this as either an administrative change or a security safeguard: stop trying random fixes, capture what you’re seeing, and contact your IT/helpdesk and your manager immediately with a clear request to confirm and restore the access you need.
Do not do these things
- Do not try to “work around” access controls (using someone else’s login, personal accounts, VPN tricks, or exporting restricted files).
- Do not repeatedly spam login/2FA attempts — it can trigger lockouts and looks like suspicious activity.
- Do not message wide groups accusing someone of misconduct; keep communications factual and private at first.
- Do not install unapproved apps/extensions “to get back in”.
- Do not delete local files, emails, or chat history in a panic.
What to do now
-
Pause and note exactly what changed (2 minutes).
Write down: the time it started, which workspace/tool (e.g., shared drive, Teams/SharePoint, Slack, Jira), what action fails (sign-in vs specific folders/channels), and the exact error message. Take a screenshot if allowed by policy. -
Check whether it’s an identity/SSO issue vs a permission issue.
- If you can’t sign in at all: note whether the failure is password, MFA, “account disabled”, or “contact admin”.
- If you can sign in but can’t see projects/files/channels: that’s usually a role/group membership change.
-
Open an urgent IT ticket (or call the helpdesk) using clear, audit-friendly wording.
Say: “My role/access appears to have changed without warning; I’ve lost access to [workspace] needed for today’s work. Please confirm whether my account was disabled/downgraded or group membership changed, restore required access, and advise if this was a security action.”
Ask for a ticket/reference number and who is assigned. -
Ask your manager (in writing) to confirm what’s going on.
Send a short message: “I’ve suddenly lost access to [workspace]. IT ticket #____ is open. Can you confirm if my role or permissions were changed and what I should do next?”
This creates a timestamped record without escalating emotionally. -
If compromise is possible, treat it as a security incident and follow your organisation’s process.
If you see unexpected MFA prompts, unfamiliar device/session notices, “impossible travel” alerts, or password reset notices you didn’t trigger:- Report it to your IT/security contact as suspected account compromise (those words matter).
- Ask them to confirm whether a security control restricted your access and to revoke active sessions/force sign-out as appropriate.
- Follow their process for password reset and device checks on managed devices.
-
If you were an admin/owner and access loss blocks operations, request a controlled handover.
Ask IT/security for the organisation’s admin recovery / break-glass route (another admin to temporarily grant access, reassign ownership, or restore a suspended user) and to log any changes they make. -
Protect today’s work without moving restricted data.
- Make a simple list of what you must deliver today and what dependencies are blocked.
- If you have drafts locally, keep them on approved storage only (managed device / approved drive).
- Inform the relevant project owner that you are blocked pending IT restore (no blame, just impact).
-
If this looks like an employment/contract change, keep it procedural.
Ask for the change and its impact (duties, access, reporting line) in writing. If you need early workplace rights guidance, you can consider speaking to your union rep (if relevant) or ACAS — but first stabilise access and clarify the immediate situation.
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 it’s disciplinary, redundancy-related, or a security mistake — get confirmation first.
Important reassurance
Sudden loss of access is common during reorganisations, license changes, group-policy updates, security actions, or admin mistakes. Feeling panicked is normal — but the safest move is to slow down, record what you see, and route it through IT and your manager so it can be corrected cleanly.
Scope note
These are first steps to stabilise the situation, avoid policy breaches, and create a clear record. Later steps (formal grievance, contract questions, data requests) may be appropriate, but they’re not the priority in the first hour.
Important note
This guide provides general, practical first-step information and is not legal, HR, or security advice. Follow your organisation’s policies and use official IT/security channels where possible.
Additional Resources
- https://www.ncsc.gov.uk/guidance/recovering-a-hacked-account
- https://www.ncsc.gov.uk/collection/using-online-services-safely/recovering-hacked-account-or-service
- https://www.acas.org.uk/changing-an-employment-contract/advice-for-employees
- https://www.acas.org.uk/changing-an-employment-contract/advice-for-employees/if-your-employer-introduces-a-contract-change-without-your-agreement
- https://www.gov.uk/your-employment-contract-how-it-can-be-changed/dealing-with-problems
- https://slack.com/intl/en-gb/help/articles/360055665434-Reactivate-your-Slack-account
- https://knowledge.workspace.google.com/admin/users/restore-a-suspended-user