Skip to content

Describe the Starter organization that chainctl develop init creates - #4283

Merged
matthewhelmke merged 2 commits into
mainfrom
set-up-starter-organization
Oct 21, 2026
Merged

matthewhelmke merged 2 commits into
mainfrom
set-up-starter-organization

Conversation

@matthewhelmke

Copy link
Copy Markdown
Collaborator

What

  • get-started/checks-and-workspaces/set-up.md: adds "What a Starter organization includes," which describes the organization chainctl develop init creates: the Starter plan, the limited_owner role, both products' allowances, and up to five non-FIPS images through Chainguard Catalog Starter, added with chainctl starter add-images once chainctl starter status shows READY. The page's "Starter organization" link now points to that section instead of the Catalog Starter page. The chainctl starter request-access paragraph now says who can send a request, who receives it, and that its link invites the coworker as viewer, which can't open sessions.
  • chainguard/workspaces/troubleshooting.md: the unable to create self-serve organization entry says the same about request-access, and points to the roles that can open sessions.

Why

The Catalog Starter page walks through the Console's sign-up for a Containers trial. Several of its statements don't hold for an organization chainctl develop init creates, so readers following the link got the wrong picture. Until the self-serve launch changes the plan pages, the set-up page describes this organization itself.

How it was checked

  • Facts come from the product team's review of the platform code deployed on 2026-10-19 and chainctl 0.2.388. chainctl starter status --help and request-access --help confirm the READY step and that a request needs a signed-in Chainguard identity. The help also says the command reports the same result when no organization matches.
  • A local Hugo build passes, the new anchor renders, every link in the changed sections resolves, and the agent-facing .md copy renders the new section as Markdown.
  • Not changed: the personal-email lines, which wait on a live test, and the GitHub sign-in line, which Say that GitHub sign-ins can create a Starter organization #4272 changes.

🤖 Generated with Claude Code

matthewhelmke and others added 2 commits October 21, 2026 12:37
The set-up page linked "Chainguard Starter" to the Catalog Starter page,
which describes a different sign-up path and doesn't fit an organization
that chainctl develop init creates. Describe that organization on the
page instead: its plan, role, allowances, and up to five images, and how
to add them. Also correct the request-access paragraph: who can send a
request, who receives it, and that its link invites the coworker as
viewer, which can't open sessions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Workspaces troubleshooting entry suggested chainctl starter
request-access without saying that its email link invites the coworker
as viewer, which can't open sessions. Say who receives the request and
point to the roles that can open sessions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@matthewhelmke
matthewhelmke requested a review from a team as a code owner October 21, 2026 17:42
@vercel

vercel Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
chainguard-docs-preview Ready Ready Preview Oct 21, 2026 5:43pm UTC
1 Skipped Deployment
Project Deployment Actions Updated
chainguard-docs Ignored Ignored Oct 21, 2026 5:43pm UTC

Request Review

@matthewhelmke
matthewhelmke merged commit 2becad8 into main Oct 21, 2026
13 checks passed
@matthewhelmke
matthewhelmke deleted the set-up-starter-organization branch October 21, 2026 17:49

This branch was successfully deployed

1 active deployment
Preview – chainguard-docs-preview — ffb0afc1 Deployed Oct 21, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants