## Summary **Batch B of Phase 3** of the H1 → front-matter migration (`DOCS-484`; parent `DOCS-477`), the editorial follow-up to Batch A (#28030). For the **124** hand-authored pages whose leading body H1 differed from the manifest nav label, this promotes the richer body H1 to the front-matter **page title** and drops the duplicate H1, while keeping the short manifest **label** as the sidebar entry. Policy agreed with the docs owner: - Short sidebar labels win. Duplicate sidebar labels are acceptable. - Identical **page titles** across two pages are not. On a collision, rename the non-generated page's title. ## Page-title collisions resolved Promoting the H1 created 4 page-title collisions; each is disambiguated by renaming the non-generated / secondary page (sidebar labels left unchanged): | page | sidebar label | body H1 | → page title | |------|---------------|---------|--------------| | `install/index.md` | Install | Installing Coder | **Install Coder in your infrastructure** | | `install/cli.md` | Coder CLI | Installing Coder | **Install the Coder CLI** | | `ai-gateway/clients/jetbrains.md` | JetBrains | JetBrains IDEs | **JetBrains** | | `workspace-access/web-ides.md` | Web IDEs and Coder Apps | Web IDEs | Web IDEs *(kept — primary user guide)* | | `extending-templates/web-ides.md` | Web IDEs and Coder Apps | Web IDEs | **Web IDEs in templates** | | `workspace-management.md` | Workspace Management | Workspaces | **Manage workspaces** *(vs generated `api/workspaces.md`)* | These titles are the only non-mechanical editorial calls in this PR. ## Deliberately excluded: generated pages `admin/security/audit-logs.md` and `admin/setup/configuration-reference.md` are `make gen` outputs (`auditdocgen` / `configdocgen`) that Phase 2 did **not** update, so a hand-added title would be reverted on the next generation. They're excluded here and need their generators taught to emit front matter first (Phase 2 pattern), tracked as `DOCS-631`. Batch A (#28030) had the same issue for three other generated pages; it has been corrected there too. ## Verification AI was the primary author of this PR (see disclosure below); per the [AI Contribution Guidelines](https://coder.com/docs/about/contributing/AI_CONTRIBUTING) here is the manual verification. - Promote = set front-matter `title` to the body H1 (or the disambiguated title above) and remove that one duplicate H1. No other body prose is reflowed. - Every added front-matter block parses as YAML; all files pass `pnpm check-docs` (markdownlint-cli2 + table formatter): `Summary: 0 error(s)`. - Removing the H1 orphaned one in-page fragment (`[MCP](#mcp)` in `ai-gateway/mcp.md`), now repointed. A cross-file fragment audit into the retitled pages found no real breakage. Anchor-change note Unlike Batch A (title unchanged, a rendered no-op), Batch B changes each page's effective title from the manifest label to the body H1, so the rendered H1 **anchor slug changes**. An audit of cross-file `.md#fragment` links into these pages surfaced no links that break as a result (the only hits were false positives against a still-present `## TLS & Reverse Proxy` heading). Same-file fragments are enforced by markdownlint MD051, which is green. ## Title casing (follow-up, DOCS-742) A follow-up commit puts the promoted titles into sentence case and removes leading gerunds (for example, `Managing workspace schedules` → `Manage workspace schedules`): 57 of the 120 titles changed, the other 63 were already compliant. Proper nouns and branded names (Coder Validated Architecture, JetBrains, File Browser, Dev Containers, Island), acronyms (API, CLI, IDE, MCP, OIDC, URL, UI, CI/CD), the Premium license tier, and maturity labels (Beta, Experimental) are preserved. The four `Nk-users` pages become `Reference architecture: up to N users` (lowercase, matching the CVA landing page's own usage); the CVA landing page keeps its branded title. `pnpm check-docs`: `Summary: 0 error(s)`. Linear: DOCS-484, DOCS-742 > This PR was created with AI assistance (Coder Agents).
5.4 KiB
title
| title |
|---|
| Shared workspaces |
Multiple users can securely connect to a single Coder workspace for programming and debugging.
Features
Workspace sharing is available to all Coder users by default, but platform admins with a Premium subscription can choose to disable sharing within their organizations or for their entire deployment.
Owners of a workspace can grant access to other users or groups with scoped roles.
This is helpful in a number of scenarios, including:
- Developers can do ad-hoc debugging or pair programming.
- A workspace can be owned by a group of users for QA, on-call rotations, or shared staging.
- AI workflows where an agent prepares a workspace and a developer takes over to review or finalize the work (ex. with Coder Agents.)
Getting Started
Workspaces can be shared through either the Coder CLI or UI.
Before you begin, ensure that you have a version of Coder with workspace sharing enabled and that your account has permission to share workspaces. This is true by default if you are an OSS user, but deployments with Premium licenses may be restricted by admins.
CLI
To share a workspace:
coder sharing share <workspace> --user alice- Shares the workspace with a single user,
alice, withusepermissions
- Shares the workspace with a single user,
coder sharing share <workspace> --user alice:admin,bob- Shares the workspace with two users -
alicewithadminpermissions, andbobwithusepermissions
- Shares the workspace with two users -
coder sharing share <workspace> --group contractor- Shares the workspace with
contractor, which is a group of users
- Shares the workspace with
To remove sharing from a workspace:
coder sharing remove <workspace> --user alice- Workspace is no longer shared with the user
alice.
- Workspace is no longer shared with the user
coder sharing remove <workspace> --group contractor- Workspace is no longer shared with the group
contractor.
- Workspace is no longer shared with the group
Important
The workspace must be restarted for the user or group removal to take effect.
To show who a workspace is shared with:
coder sharing status <workspace>
To list shared workspaces:
coder list --search shared:truecoder list --search shared_with_user:mecoder list --search shared_with_user:<user>coder list --search shared_with_group:<group>
UI
Sharing your Workspace
-
Open a workspace that you own.
-
Locate and select the 'Share' button.
- Add the users or groups that you want to share the workspace with. For each one, select a role.
useallows for connection via SSH and apps, the ability to start and stop the workspace, view logs and stats, and update on start when required.adminallows for all of the above, as well as the ability to rename the workspace, update at any time, and invite others with theuserole.- Neither role allows for the user to delete the workspace.
- After removing a user/group, a workspace restart is required for the removal to take effect.
Using a shared workspace
Once a workspace is shared, you can find the shared workspace by filtering for "Shared" in the Workspaces page.
Accessing workspace apps in shared workspaces
Sharing a workspace grants SSH and terminal access to other users. However, workspace apps like code-server may return a 404 page for non-owners depending on how the app is routed.
By default, workspace apps that don't set subdomain = true use path-based
routing (e.g., coder.example.com/@user/workspace/apps/code-server/).
Path-based apps share the same origin as the Coder dashboard, so Coder blocks
non-owners from accessing them to prevent
cross-site scripting risks.
This restriction applies even when the user has been granted access through
workspace sharing.
To allow other users to access workspace apps, configure subdomain-based access:
-
Set a wildcard access URL on your deployment (e.g.,
CODER_WILDCARD_ACCESS_URL=*.coder.example.com). -
Set
subdomain = trueon the workspace app. For example, if you use the code-server module:module "code-server" { source = "registry.coder.com/coder/code-server/coder" agent_id = coder_agent.main.id subdomain = true # ... }
Subdomain-based apps run in an isolated browser security context, so Coder allows other users to access them without additional configuration.
Policies
There are several sharing policy levels that can be selected on a per-organization basis.
- Everyone – Anybody can share their workspace with any individual or group in the same organization.
- Service Accounts Only – Only workspaces owned by service accounts can be shared with any individual or group in the same organization.
- Disabled – Workspaces within the organization cannot be shared.
The Disabled policy can also be applied to the entire deployment by setting the CODER_DISABLE_WORKSPACE_SHARING environment variable, or by using the corresponding command argument or config value.


