Repository navigation
Say that creating a Starter organization takes a work email address - #4198
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
The getting-started pages and the chainctl develop init reference described creating a Starter organization with a personal email address. That path is behind ENABLE_UNVERIFIED_STARTER_ORGS, which is off in production, so `chainctl develop init` creates organizations only for work email addresses. State that a work email address is required, drop the personal-email naming and invite text and the --name row in the sign-up flags table, and describe --name as having no effect in the reference. Part of DOCS-268. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
matthewhelmke
force-pushed
the
starter-work-email-only
branch
from
October 13, 2026 16:02
7778090 to
5946b36
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Checks and Workspaces docs describe creating a Starter organization with a personal email address. That path isn't live. An engineer in #eng-customer-platform confirmed that
ENABLE_UNVERIFIED_STARTER_ORGSis off in production (https://chainguard-dev.slack.com/archives/C0AH52T1SKC/p1791898344531879), and this week's code freeze keeps it off through the October 14 launch. This PR makes the docs match production before launch. Part of DOCS-268.Changes
--namerow, which only applied to personal-email sign-ups.chainctl develop initreference keeps--name, because the flag exists, but describes it as having no effect.not eligible for a self-serve Starter organizationerror says the same about work email.The invite steps for Starter organizations are unchanged and correct: invites are limited to the organization's email domain.
Not changed
"Chainguard Starter" still links to the Catalog Starter page. Whether the org
develop initcreates needs its own description is still open in DOCS-268.Testing
The Hugo build is clean, and the sign-up flags table renders without the
--namerow. No other page mentions naming an organization at sign-up.🤖 Generated with Claude Code