Rebuild an Edge Workspace Workflow After Shared Workspaces Change
Older instructions for Edge Workspaces describe inviting colleagues to a shared set of tabs. Microsoft’s current documentation describes a newer version for individual use: sharing, joining and invitations are no longer supported. Confirm the version and current feature before treating a missing invitation button as a broken installation.
Preserve the useful project structure
List the links your project actually needs, giving each a recognisable label. Include the working document’s stable service link rather than a temporary download address. Keep this list somewhere appropriate for the project before reorganising or deleting any workspace.
In current Edge, use the tab-search control and Manage workspaces. Create a blank workspace or one from the intended open tabs, then give it a clear project name. Microsoft’s new-workspace guidance requires a supported desktop platform, Edge 144 or later and a signed-in account.
Open the resulting workspace and check each essential tab. Confirm the website’s own account and access rights; a saved project tab does not grant document permission or select the correct organisation inside a service.
Separate personal organisation from team access
If colleagues need the project materials, use the document service’s established sharing process or a maintained project-link list with appropriate permissions. Do not assume that putting a private document in your personal workspace makes it visible to the team.
To use your workspace on another authorised device, inspect Edge’s profile Sync settings, including Workspaces and Tab Groups. Check the actual project appears and that its important links open. The new version does not rely on the former OneDrive-storage requirement described in older instructions.
Close and reopen the workspace to verify that the intended tab set remains useful. Save ongoing work inside each application; workspace organisation is not a backup of document edits. Delete obsolete workspaces only after the necessary links and team-sharing arrangements have been checked, so an interface transition does not become a lost project reference.
Sources: Microsoft Support.