Files
coder/docs/admin/integrations/island.md
T
Nick Vigilante 7846490770 docs: reconcile H1/label mismatches into front-matter titles (Phase 3) (#28036)
## 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).
2026-09-08 16:34:00 +00:00

6.1 KiB

title
title
Island browser integration
April 24, 2024

Island is an enterprise-grade browser, offering a Chromium-based experience similar to popular web browsers like Chrome and Edge. It includes built-in security features for corporate applications and data, aiming to bridge the gap between consumer-focused browsers and the security needs of the enterprise.

Coder natively integrates with Island's feature set, which include data loss protection (DLP), application awareness, browser session recording, and single sign-on (SSO). This guide intends to document these feature categories and how they apply to your Coder deployment.

General Configuration

Create an Application Group for Coder

We recommend creating an Application Group specific to Coder in the Island Management console. This Application Group object will be referenced when creating browser policies.

See the Island documentation for creating an Application Group.

Advanced Data Loss Protection

Integrate Island's advanced data loss prevention (DLP) capabilities with Coder's cloud development environment (CDE), enabling you to control the "last mile" between developers' CDE and their local devices, ensuring that sensitive IP remains in your centralized environment.

Block cut, copy, paste, printing, screen share

  1. Create a Data Sandbox Profile.

  2. Configure the following actions to allow/block (based on your security requirements).

    • Screenshot and Screen Share
    • Printing
    • Save Page
    • Clipboard Limitations
  3. Create a Policy Rule to apply the Data Sandbox Profile.

  4. Define the Coder Application group as the Destination Object.

  5. Define the Data Sandbox Profile as the Action in the Last Mile Protection section.

Conditionally allow copy on Coder's CLI authentication page

  1. Create a URL Object with the following configuration.

    • Include
    • URL type: Wildcard
    • URL address: coder.example.com/cli-auth
    • Casing: Insensitive
  2. Create a Data Sandbox Profile.

  3. Configure action to allow copy/paste.

  4. Create a Policy Rule to apply the Data Sandbox Profile.

  5. Define the URL Object you created as the Destination Object.

  6. Define the Data Sandbox Profile as the Action in the Last Mile Protection section.

Prevent file upload/download from the browser

  1. Create a Protection Profiles for both upload/download.

  2. Create a Policy Rule to apply the Protection Profiles.

  3. Define the Coder Application group as the Destination Object.

  4. Define the applicable Protection Profile as the Action in the Data Protection section.

Scan files for sensitive data

  1. Create a Data Loss Prevention scanner.

  2. Create a Policy Rule to apply the DLP Scanner.

  3. Define the Coder Application group as the Destination Object.

  4. Define the DLP Scanner as the Action in the Data Protection section.

Application Awareness and Boundaries

Ensure that Coder is only accessed through the Island browser, guaranteeing that your browser-level DLP policies are always enforced, and developers can't sidestep such policies simply by using another browser.

Configure browser enforcement, conditional access policies

Create a conditional access policy for your configured identity provider.

Note that the configured IdP must be the same for both Coder and Island.

Browser Activity Logging

Govern and audit in-browser terminal and IDE sessions using Island, such as screenshots, mouse clicks, and keystrokes.

Activity Logging Module

  1. Create an Activity Logging Profile. Supported browser events include:

    • Web Navigation
    • File Download
    • File Upload
    • Clipboard/Drag & Drop
    • Print
    • Save As
    • Screenshots
    • Mouse Clicks
    • Keystrokes
  2. Create a Policy Rule to apply the Activity Logging Profile.

  3. Define the Coder Application group as the Destination Object.

  4. Define the Activity Logging Profile as the Action in the Security & Visibility section.

Identity-aware logins (SSO)

Integrate Island's identity management system with Coder's authentication mechanisms to enable identity-aware logins.

Configure single sign-on (SSO) seamless authentication between Coder and Island

Configure the same identity provider (IdP) for both your Island and Coder deployment. Upon initial login to the Island browser, the user's session token will automatically be passed to Coder and authenticate their Coder session.