Team cannot see a workspace they used last week: troubleshooting guide

TL;DR — If your team cannot see a workspace they used last week, the most common cause is that they are signed into the wrong account or organization, or the workspace was archived or moved. Start by checking the active email address, active organization/team switcher, and any "Archived" or ownership filters before assuming data was lost. Reading time: ~6 min

The scenario

It is a normal Tuesday afternoon. You open the app to pick up work from last week, but the workspace your team was actively using is gone from the list. One teammate can still see it on their screen, another gets a "You do not have access" message, and now everyone is asking whether the workspace was deleted. You need to work out quickly whether this is a sign-in issue, a permissions change, a filter problem, or a real removal.

Symptoms

• The workspace does not appear in the main workspace list.
• You see messages like:

You do not have access to this workspace

Workspace not found

This resource has been archived

Your session has expired

• A direct link opens a sign-in page instead of the workspace.
• One teammate can see the workspace, but another teammate cannot.
• The workspace appears for an admin, but not for regular members.
• Search returns no results until filters are cleared.
• Audit or activity logs show membership changes, role changes, SSO (single sign-on) re-provisioning, or workspace archival.

Likely causes

Step-by-step diagnosis

1. Confirm the signed-in account and current organization/team

   • Dashboard path: click your avatar/profile menu in the top-right area of the app, then check the email address and current organization/team name.
   • If your app has an organization switcher, open it and look for the organization where you used the workspace last week.
   • This is your problem if: the email is different from the one your team normally uses, or the active organization/team is different.
   • Jump to: Fixes → Wrong account or wrong organization/team

2. Clear filters and check hidden or archived views

   • Dashboard path: Workspace list → Search/Filters → Clear all. Then open any tabs or dropdowns labeled "Archived", "Hidden", "Inactive", or "All workspaces".
   • This is your problem if: the workspace appears after clearing filters, or it is visible only under "Archived".
   • Jump to: Fixes → Workspace is filtered, archived, or hidden

3. Open a direct link to the workspace

   • Ask a teammate who can still see the workspace to copy the workspace URL and send it to you.
   • Open it in a private/incognito browser window, then sign in.
   • This is your problem if: the direct link says "You do not have access" or sends you into a different organization after sign-in.
   • Jump to: Fixes → Membership or role was removed or Fixes → Wrong account or wrong organization/team

4. Check membership in the app's admin area

   • Dashboard path: Settings → Members, Users, People, or Access. Search for the affected user's email.
   • Check both the organization/team membership and the workspace-level membership if your app separates them.
   • This is your problem if: the user is missing, marked suspended, or has a lower role than before.
   • Jump to: Fixes → Membership or role was removed

5. Check identity provider assignment if you use SSO

   • Dashboard path: in your identity provider admin portal (for example, Okta, Microsoft Entra ID, Google Admin), search for the user and confirm they are still assigned to the app and the correct group.
   • If your setup uses SCIM (automatic user provisioning), check whether the user was deprovisioned or moved out of the access group.
   • This is your problem if: the user is unassigned, disabled, or no longer in the required group.
   • Jump to: Fixes → Identity provider or SSO sync changed access

6. Check whether the workspace was moved to another owner or organization

   • Ask a current admin who can still see the workspace to open Workspace Settings → General, Details, or Ownership.
   • This is your problem if: the owner, billing account, or organization/team changed since last week.
   • Jump to: Fixes → Workspace was transferred to another owner or organization

7. Review audit logs for deletion or archival

   • Dashboard path: Admin/Settings → Audit Log, Activity Log, or Security Log. Search the workspace name and the last 7-14 days.
   • Look for events like:

workspace.archived
workspace.deleted
member.removed
role.changed
sso.deprovisioned

• This is your problem if: you find a deletion, archival, or removal event matching the time the workspace disappeared.
• Jump to: Fixes → Workspace was deleted or retention expired

Fixes

Wrong account or wrong organization/team

1. Sign out completely.
2. Sign back in with the exact email address that had access last week.
3. After sign-in, use the organization/team switcher to select the correct organization.
4. If your browser keeps auto-signing you into the wrong identity, use a private/incognito window and sign in manually.
5. If you use Google or Microsoft sign-in, choose the correct account at the account picker instead of the default one.

If you need to confirm which account was used before, ask a teammate to check the member list and copy the exact email address shown there.

Verify it worked: the workspace appears in the normal list or the direct workspace URL opens without an access error.

Workspace is filtered, archived, or hidden

1. Open the workspace list.
2. Clear search text and all filters.
3. Switch the list view from personal/favorites/recent to all workspaces.
4. Open the archived or hidden section.
5. If the workspace is archived and you have permission, use the workspace action menu to restore or unarchive it.

If your app supports search by ID and a teammate can provide it, search by the exact workspace name or ID instead of a partial name.

Verify it worked: the workspace is visible in the main list under "All" or "Active" and teammates can open it normally.

Membership or role was removed or downgraded

1. Have an admin open Settings → Members/Users.
2. Search for the affected user's email.
3. If the user is missing, use the invite or add-member action and re-add them.
4. If the user is present but has the wrong role, change it back to the required role for that workspace.
5. If the app has both organization access and workspace access, confirm both are present.

If your platform also exposes an API, an admin can often confirm membership with a simple request like this after generating an API token in the dashboard:

curl -H "Authorization: Bearer YOUR_TOKEN" https://api.example.com/workspaces/WORKSPACE_ID/members

Replace the URL with your vendor's documented endpoint only if your app supports it.

Verify it worked: the user appears in the member list with the correct role and can open the workspace link.

Identity provider or SSO sync changed access

1. In your identity provider admin portal, search for the affected user.
2. Confirm the user is active and assigned to the application.
3. Confirm the user is still in the group that grants access.
4. If SCIM provisioning is enabled, run a manual reprovision/resync from the identity provider side if your provider offers that action.
5. Ask the user to sign out and sign back in after the assignment is fixed.

For Microsoft Entra ID or Okta-style setups, the key checks are always the same: user active, app assignment present, correct group membership present.

Verify it worked: after a fresh sign-in, the user lands in the correct organization and the workspace becomes visible.

Workspace was transferred to another owner or organization

1. Ask a current admin who can still access the workspace to open Workspace Settings.
2. Check the current owner and organization/team.
3. If the workspace was moved, add the missing users to the new organization/team and then to the workspace if needed.
4. Update any saved bookmarks so the team uses the new workspace URL if it changed.

⚠️ If ownership changes affect billing or legal ownership, confirm internally before moving it back. Reversing ownership can affect who can administer or export data.

Verify it worked: the affected users appear in the new organization/team and can access the workspace from the updated URL.

Workspace was deleted or retention expired

1. Open the audit log and confirm the deletion or archival event.
2. Check whether your app has a trash, recycle bin, or restore window in the admin area.
3. If a restore option exists, restore the workspace from the dashboard.
4. If there is no self-service restore, contact the software agency's support team with:
   • workspace name
   • approximate last seen date/time
   • organization/team name
   • affected user emails
   • any audit log event IDs

⚠️ Do not create a new workspace with the same name until support confirms recovery options. A replacement workspace can confuse users and complicate recovery.

Verify it worked: the workspace reappears with its original content and the audit log shows a restore event.

Prevention

• Record the workspace ID and owner in an internal doc. Keep a simple table with workspace name, URL, owner, and organization/team. Example:

[
  {
    "workspace_name": "Client Alpha",
    "workspace_url": "https://app.example.com/workspaces/ws_12345",
    "owner_email": "ops@yourcompany.com",
    "org_name": "Agency Production"
  }
]

• Review access changes weekly in the audit log. Put a recurring calendar task in place for an admin to check member removals, role changes, and archival events from the last 7 days.
• Tie access to groups, not individual users, in your identity provider. For example, grant the app to a group like agency-workspace-users and manage membership there instead of one-off assignments.

Group: agency-workspace-users
Assigned app: Your workspace app
Members: team emails who should retain access

• Add an offboarding checklist that includes workspace transfer review. Before removing a user, confirm whether they own any active workspaces and transfer ownership first.
• Keep at least two admins per organization/team. This prevents a single admin departure from leaving the workspace inaccessible.
• Save a direct workspace URL in your project tracker. A direct link helps you quickly tell the difference between "missing from the list" and "permission denied" during an incident.

If none of the checks above explain the problem, send support a short incident note with the exact error message, affected emails, workspace name, direct URL, and a screenshot of the member list or audit event. That usually cuts resolution time dramatically.

This article was written by an AI system and published pending human review. Verify anything you intend to act on.