## 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).
6.5 KiB
title
| title |
|---|
| Organizations (Premium) |
Note
Organizations requires a Premium license. For more details, contact your account team.
Organizations can be used to segment and isolate resources inside a Coder deployment for different user groups or projects.
Example
Here is an example of how one could use organizations to run a Coder deployment with multiple platform teams, all with unique resources:
For more information about how to use organizations, visit the organizations best practices guide.
The default organization
All Coder deployments start with one organization called coder. All new users
are added to this organization by default.
To edit the organization details, select Admin settings from the top bar, then Organizations:
From there, you can manage the name, icon, description, users, and groups:
Additional organizations
Any additional organizations have unique admins, users, templates, provisioners, groups, and workspaces. Each organization must have at least one dedicated provisioner since the built-in provisioners only apply to the default organization.
You can configure organization/role/group sync from your identity provider to avoid manually assigning users to organizations.
How to create an organization
Prerequisites
- Coder v2.16+ deployment with Premium license and Organizations enabled (contact your account team) for more details.
- User with
Ownerrole
1. Create the organization
To create a new organization:
-
Select Admin settings from the top bar, then Organizations.
-
Select the current organization to expand the organizations dropdown, then select Create Organization:
-
Enter the details and select Save to continue:
In this example, we'll create the data-platform org.
Next deploy a provisioner and template for this organization.
2. Deploy a provisioner
Provisioners are organization-scoped and are responsible for executing Terraform/OpenTofu to provision the infrastructure for workspaces and testing templates. Before creating templates, we must deploy at least one provisioner as the built-in provisioners are scoped to the default organization.
-
Using Coder CLI, run the following command to create a key that will be used to authenticate the provisioner:
coder provisioner keys create data-cluster-key --org data-platform Successfully created provisioner key data-cluster! Save this authentication token, it will not be shown again. < key omitted > -
Start the provisioner with the key on your desired platform.
In this example, start the provisioner using the Coder CLI on a host with Docker. For instructions on using other platforms like Kubernetes, see our provisioner documentation.
export CODER_URL=https://<your-coder-url> export CODER_PROVISIONER_DAEMON_KEY=<key> coder provisionerd start --org <org-name>
3. Create a template
Once you've started a provisioner, you can create a template. You'll notice the Create Template screen now has an organization dropdown:
4. Add members
From Admin settings, select Organizations, then Members to add members to your organization. Once added, members will be able to see the organization-specific templates.
5. Create a workspace
Now, users in the data platform organization will see the templates related to their organization. Users can be in multiple organizations.
Default member roles
Note
Editing default member roles requires a Premium license. (learn more).
Each organization carries a default_org_member_roles list of built-in role
names. Coder unions this list into every member's effective roles at request
time, so changes propagate to all current and future members on their next
request without re-issuing tokens or editing per-user role assignments.
The default value is ["organization-workspace-access"]. With that default,
every organization member can read, build, ssh into, and execute commands in
workspaces they own. Removing organization-workspace-access from the list
creates organization members that cannot create or use workspaces unless the
role is assigned to them directly, which is useful for restricted accounts
that should only hold the minimal member permissions.
To edit the default roles in the dashboard, go to Admin settings > Organizations > Roles > Default Roles.
From the CLI, use coder organizations edit:
coder organizations edit --org <organization> \
--default-org-member-roles organization-workspace-access,organization-template-admin
The flag replaces the current list rather than adding to it, and accepts a
comma-separated list of built-in role names. Pass an empty value to remove
every role. Removing a role prompts for confirmation unless you pass
--yes.
You can also set default_org_member_roles via
PATCH /organizations/{organization}.
Limitations
default_org_member_rolesaccepts built-in role names only. Custom organization roles are rejected; assign them directly to members instead.- Removing a role from the list removes it from every member that does not hold the role through a direct assignment, including existing members. Review the per-organization audit log if you need to trace who changed the defaults.



