Add Enterprise Portal (New) docs section by AmberAlston · Pull Request #4066 · replicatedhq/replicated-docs

AmberAlston · 2026-05-14T18:38:32Z

Preview - new section https://deploy-preview-4066--replicated-docs-upgrade.netlify.app/vendor/enterprise-portal-v2-about

Summary

Splits the Enterprise Portal sidebar into two sections: Classic and New (Alpha)
Adds (Classic) labels and callout notes to the 6 existing EP pages pointing vendors to the new docs
Creates 12 new pages for the new Enterprise Portal covering:
- About (overview, what's new, limitations, requirements, migration guide)
- Connect a Git Repo
- Customize Portal Content (template structure, toc.yaml, MDX components, template variables, visibility, assets)
- Customize Portal Branding (theme.yaml reference)
- Versioned Docs (branch model, version resolution, pinning, channel gating)
- Helm Reference Docs (auto-generated chart reference)
- Terraform Modules (premium feature: module reference docs, proxy registry)
- Preview the Enterprise Portal (local CLI preview)
- Manage Customer Access (invitations, domain restrictions, SAML, service accounts, emails)
- Enable Self-Service Sign-Ups
- View a Customer's Enterprise Portal (login as customer)
- Log in to and Use the Enterprise Portal (customer-facing experience, troubleshooting)

Notes

All New pages include an alpha banner
Terraform Modules page is additionally marked as a premium feature
"Classic" / "New" naming matches the Vendor Portal toggle language
Security Center stays in its own top-level section (spans both VP and EP)
Structure proposal reviewed and approved by Paige
Screenshots will be added later as we get closer to beta. Text content is the focus of this initial draft.

Vale linter changes

Added the following terms to styles/config/vocabularies/TechJargon/accept.txt: repo, repos, repo's, semver, frontmatter, callout, callouts, signups, enum, unpublish, PDFs, URIs. Paige, please review the accept list additions directly to make sure these are acceptable.

Remaining vale warnings (passive voice, sentence length) were left as-is since the v1 EP docs follow the same patterns.

Test plan

Verify sidebar renders both Classic and New sections correctly
Verify all Classic pages show the callout note linking to New docs
Verify all internal cross-links between New pages resolve correctly
Verify Docusaurus build succeeds with no broken links
Review content accuracy against current alpha feature state
Review TechJargon accept list additions

🤖 Generated with Claude Code

Split Enterprise Portal docs into two sidebar sections: - Enterprise Portal (Classic): existing v1 pages with (Classic) title labels and callout notes pointing to the new docs - Enterprise Portal (New) (Alpha): 12 new pages covering content repo setup, MDX components, versioned docs, Helm reference, Terraform modules, preview, customer access, and more Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

netlify · 2026-05-14T18:38:37Z

✅ Deploy Preview for replicated-docs ready!

Name	Link
🔨 Latest commit	`0b48f0d`
🔍 Latest deploy log	https://app.netlify.com/projects/replicated-docs/deploys/6a063d97c8e454000832343e
😎 Deploy Preview	https://deploy-preview-4066--replicated-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

netlify · 2026-05-14T18:38:38Z

✅ Deploy Preview for replicated-docs-upgrade ready!

Name	Link
🔨 Latest commit	`0b48f0d`
🔍 Latest deploy log	https://app.netlify.com/projects/replicated-docs-upgrade/deploys/6a063d97a38bd600088a9622
😎 Deploy Preview	https://deploy-preview-4066--replicated-docs-upgrade.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

github-actions

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

vale

docs/vendor/enterprise-portal-v2-branding.mdx|1 col 3| [Replicated.Headings] 'Customize Portal Branding (New)' should use sentence case.
docs/vendor/enterprise-portal-v2-branding.mdx|7 col 40| [Replicated.Passive] In general, use active voice instead of passive voice ('is configured').
docs/vendor/enterprise-portal-v2-branding.mdx|7 col 84| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-branding.mdx|7 col 172| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-branding.mdx|11 col 4| [Replicated.Headings] 'theme.yaml Reference' should use sentence case.
docs/vendor/enterprise-portal-v2-branding.mdx|14 col 26| [Replicated.Passive] In general, use active voice instead of passive voice ('be nested').
docs/vendor/enterprise-portal-v2-branding.mdx|14 col 36| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'under'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-branding.mdx|47 col 4| [Replicated.Headings] 'Branding Fields' should use sentence case.
docs/vendor/enterprise-portal-v2-branding.mdx|59 col 18| [Vale.Spelling] Did you really mean 'enum'?
docs/vendor/enterprise-portal-v2-branding.mdx|72 col 4| [Replicated.Headings] 'Login Page Footer' should use sentence case.
docs/vendor/enterprise-portal-v2-branding.mdx|74 col 190| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-branding.mdx|79 col 76| [Replicated.Passive] In general, use active voice instead of passive voice ('is recommended').
docs/vendor/enterprise-portal-v2-connect-repo.mdx|1 col 3| [Replicated.Headings] 'Connect a Git Repo (New)' should use sentence case.
docs/vendor/enterprise-portal-v2-connect-repo.mdx|1 col 17| [Vale.Spelling] Did you really mean 'Repo'?
docs/vendor/enterprise-portal-v2-connect-repo.mdx|7 col 27| [Replicated.Passive] In general, use active voice instead of passive voice ('is driven').
docs/vendor/enterprise-portal-v2-connect-repo.mdx|7 col 49| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-connect-repo.mdx|7 col 80| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-connect-repo.mdx|16 col 125| [Vale.Spelling] Did you really mean 'repos'?
docs/vendor/enterprise-portal-v2-connect-repo.mdx|16 col 131| [Replicated.Acronyms] Spell out 'AND' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-connect-repo.mdx|16 col 152| [Vale.Spelling] Did you really mean 'repos'?
docs/vendor/enterprise-portal-v2-connect-repo.mdx|16 col 160| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-connect-repo.mdx|16 col 200| [Vale.Spelling] Did you really mean 'repos'?
docs/vendor/enterprise-portal-v2-connect-repo.mdx|21 col 16| [Vale.Spelling] Did you really mean 'Repo'?
docs/vendor/enterprise-portal-v2-connect-repo.mdx|27 col 4| [Replicated.Headings] 'Step 3: Link Repository' should use sentence case.
docs/vendor/enterprise-portal-v2-connect-repo.mdx|32 col 99| [Replicated.Passive] In general, use active voice instead of passive voice ('is found').
docs/vendor/enterprise-portal-v2-connect-repo.mdx|32 col 109| [Replicated.Timeless] Avoid temporal words like 'you'll'.
docs/vendor/enterprise-portal-v2-connect-repo.mdx|32 col 134| [Replicated.Timeless] Avoid temporal words like 'won't'.
docs/vendor/enterprise-portal-v2-connect-repo.mdx|32 col 160| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-connect-repo.mdx|35 col 14| [Replicated.Passive] In general, use active voice instead of passive voice ('are synced').
docs/vendor/enterprise-portal-v2-connect-repo.mdx|35 col 71| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-connect-repo.mdx|37 col 190| [Replicated.Passive] In general, use active voice instead of passive voice ('is shown').
docs/vendor/enterprise-portal-v2-connect-repo.mdx|56 col 23| [Replicated.Passive] In general, use active voice instead of passive voice ('be named').
docs/vendor/enterprise-portal-v2-connect-repo.mdx|56 col 37| [Vale.Spelling] Did you really mean 'semver'?
docs/vendor/enterprise-portal-v2-connect-repo.mdx|56 col 91| [Vale.Spelling] Did you really mean 'version_label'?
docs/vendor/enterprise-portal-v2-connect-repo.mdx|56 col 129| [Replicated.Passive] In general, use active voice instead of passive voice ('is synced').
docs/vendor/enterprise-portal-v2-helm-reference.mdx|1 col 3| [Replicated.Headings] 'Helm Reference Docs (New)' should use sentence case.
docs/vendor/enterprise-portal-v2-helm-reference.mdx|7 col 156| [Replicated.Passive] In general, use active voice instead of passive voice ('is required').
docs/vendor/enterprise-portal-v2-helm-reference.mdx|36 col 158| [Replicated.WordSwaps] Use 'after' or 'one time' instead of 'once'.
docs/vendor/enterprise-portal-v2-helm-reference.mdx|41 col 4| [Replicated.Headings] 'Generated Content' should use sentence case.
docs/vendor/enterprise-portal-v2-helm-reference.mdx|46 col 71| [Vale.Spelling] Did you really mean 'callouts'?
docs/vendor/enterprise-portal-v2-helm-reference.mdx|48 col 105| [Vale.Spelling] Did you really mean 'dev'?
docs/vendor/enterprise-portal-v2-helm-reference.mdx|49 col 76| [Replicated.Passive] In general, use active voice instead of passive voice ('were added').
docs/vendor/enterprise-portal-v2-helm-reference.mdx|51 col 4| [Replicated.Headings] 'Controlling Values Visibility' should use sentence case.
docs/vendor/enterprise-portal-v2-preview.mdx|1 col 3| [Replicated.Headings] 'Preview the Enterprise Portal (New)' should use sentence case.
docs/vendor/enterprise-portal-v2-preview.mdx|7 col 75| [Replicated.Timeless] Avoid temporal words like 'they'll'.
docs/vendor/enterprise-portal-v2-preview.mdx|9 col 4| [Replicated.Headings] 'Local Preview' should use sentence case.
docs/vendor/enterprise-portal-v2-preview.mdx|13 col 85| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-preview.mdx|21 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-preview.mdx|23 col 8| [Replicated.Passive] In general, use active voice instead of passive voice ('are authenticated').
docs/vendor/enterprise-portal-v2-preview.mdx|25 col 56| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-preview.mdx|27 col 175| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-preview.mdx|29 col 4| [Replicated.Headings] 'Common Options' should use sentence case.
docs/vendor/enterprise-portal-v2-preview.mdx|38 col 180| [Replicated.Passive] In general, use active voice instead of passive voice ('is expected').
docs/vendor/enterprise-portal-v2-preview.mdx|38 col 220| [Replicated.Passive] In general, use active voice instead of passive voice ('be committed').
docs/vendor/enterprise-portal-use.mdx|1 col 3| [Replicated.Headings] 'Log in to and Use the Enterprise Portal (Classic)' should use sentence case.
docs/vendor/enterprise-portal-v2-invite.mdx|1 col 3| [Replicated.Headings] 'Manage Customer Access (New)' should use sentence case.
docs/vendor/enterprise-portal-v2-invite.mdx|9 col 4| [Replicated.Headings] 'Enabling Enterprise Portal for Customers' should use sentence case.
docs/vendor/enterprise-portal-v2-invite.mdx|11 col 88| [Replicated.Passive] In general, use active voice instead of passive voice ('is controlled').
docs/vendor/enterprise-portal-v2-invite.mdx|17 col 133| [Replicated.Passive] In general, use active voice instead of passive voice ('is needed').
docs/vendor/enterprise-portal-v2-invite.mdx|19 col 4| [Replicated.Headings] 'Inviting Users' should use sentence case.
docs/vendor/enterprise-portal-v2-invite.mdx|30 col 4| [Replicated.Headings] 'Removing Users' should use sentence case.
docs/vendor/enterprise-portal-v2-invite.mdx|35 col 67| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'next to'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-invite.mdx|38 col 4| [Replicated.Headings] 'Domain Restrictions' should use sentence case.
docs/vendor/enterprise-portal-v2-invite.mdx|40 col 34| [Replicated.Passive] In general, use active voice instead of passive voice ('be invited').
docs/vendor/enterprise-portal-v2-invite.mdx|46 col 64| [Replicated.Passive] In general, use active voice instead of passive voice ('be invited').
docs/vendor/enterprise-portal-v2-invite.mdx|48 col 4| [Replicated.Headings] 'SAML Authentication (Alpha)' should use sentence case.
docs/vendor/enterprise-portal-v2-invite.mdx|56 col 67| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-invite.mdx|58 col 4| [Replicated.Headings] 'Service Accounts' should use sentence case.
docs/vendor/enterprise-portal-v2-invite.mdx|62 col 87| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'under'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-invite.mdx|63 col 20| [Replicated.Passive] In general, use active voice instead of passive voice ('are created').
docs/vendor/enterprise-portal-v2-invite.mdx|66 col 4| [Replicated.Headings] 'Email History' should use sentence case.
docs/vendor/enterprise-portal-configure.mdx|1 col 3| [Replicated.Headings] 'Customize the Enterprise Portal (Classic)' should use sentence case.
docs/vendor/enterprise-portal-configure.mdx|3 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-configure.mdx|6 col 49| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|1 col 3| [Replicated.Headings] 'Enable Self-Service Sign-Ups (New)' should use sentence case.
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|9 col 4| [Replicated.Headings] 'Configuring Self-Service Sign-Ups' should use sentence case.
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|13 col 52| [Replicated.Passive] In general, use active voice instead of passive voice ('is assigned').
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|16 col 54| [Replicated.Passive] In general, use active voice instead of passive voice ('are enabled').
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|20 col 35| [Replicated.Passive] In general, use active voice instead of passive voice ('is generated').
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|22 col 4| [Replicated.Headings] 'Custom Signup Fields' should use sentence case.
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|30 col 52| [Replicated.Passive] In general, use active voice instead of passive voice ('be filled').
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|32 col 12| [Replicated.Passive] In general, use active voice instead of passive voice ('is assigned').
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|32 col 162| [Vale.Spelling] Did you really mean 'signups'?
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|34 col 4| [Replicated.Headings] 'Signup Flow (Customer Experience)' should use sentence case.
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|39 col 21| [Replicated.Passive] In general, use active voice instead of passive voice ('are configured').
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|40 col 26| [Replicated.Passive] In general, use active voice instead of passive voice ('are configured').
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|42 col 56| [Replicated.Passive] In general, use active voice instead of passive voice ('is activated').
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|44 col 13| [Vale.Spelling] Did you really mean 'Signups'?
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|46 col 27| [Vale.Spelling] Did you really mean 'signups'?
docs/vendor/enterprise-portal-v2-content.mdx|1 col 3| [Replicated.Headings] 'Customize Portal Content (New)' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|7 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-content.mdx|11 col 1| [Replicated.Headings] 'Content Template Structure *****************************' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|94 col 4| [Replicated.Headings] 'Table of Contents' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|96 col 41| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-content.mdx|100 col 46| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-content.mdx|105 col 83| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-content.mdx|109 col 5| [Replicated.Headings] 'Complete Example' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|111 col 1| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'Here'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-content.mdx|155 col 1| [Replicated.Headings] 'MDX Components *****************' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|159 col 5| [Replicated.Headings] 'Layout and Callouts' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|159 col 16| [Vale.Spelling] Did you really mean 'Callouts'?
docs/vendor/enterprise-portal-v2-content.mdx|161 col 29| [Vale.Spelling] Did you really mean 'callout'?
docs/vendor/enterprise-portal-v2-content.mdx|177 col 26| [Vale.Spelling] Did you really mean 'callout'?
docs/vendor/enterprise-portal-v2-content.mdx|253 col 5| [Replicated.Headings] 'Installation Components' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|257 col 170| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-content.mdx|274 col 34| [Replicated.Passive] In general, use active voice instead of passive voice ('are personalized').
docs/vendor/enterprise-portal-v2-content.mdx|334 col 5| [Replicated.Headings] 'Update Components' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|346 col 75| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-content.mdx|347 col 75| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'above'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-content.mdx|348 col 76| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-content.mdx|351 col 91| [Replicated.Passive] In general, use active voice instead of passive voice ('is stripped').
docs/vendor/enterprise-portal-v2-content.mdx|353 col 11| [Replicated.Passive] In general, use active voice instead of passive voice ('be combined').
docs/vendor/enterprise-portal-v2-content.mdx|353 col 50| [Replicated.Acronyms] Spell out 'AND' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-content.mdx|353 col 124| [Replicated.Passive] In general, use active voice instead of passive voice ('be parsed').
docs/vendor/enterprise-portal-v2-content.mdx|353 col 147| [Replicated.Passive] In general, use active voice instead of passive voice ('is hidden').
docs/vendor/enterprise-portal-v2-content.mdx|436 col 4| [Replicated.Headings] 'High Availability Setup' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|451 col 4| [Replicated.Headings] 'Acme-Specific Configuration' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|474 col 4| [Replicated.Headings] 'High Availability Setup' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|502 col 5| [Replicated.Headings] 'Page-Level Visibility (Frontmatter)' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|502 col 28| [Vale.Spelling] Did you really mean 'Frontmatter'?
docs/vendor/enterprise-portal-v2-content.mdx|504 col 52| [Vale.Spelling] Did you really mean 'frontmatter'?
docs/vendor/enterprise-portal-v2-content.mdx|519 col 68| [Vale.Spelling] Did you really mean 'frontmatter'?
docs/vendor/enterprise-portal-v2-content.mdx|519 col 81| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-content.mdx|519 col 229| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-content.mdx|521 col 4| [Replicated.Headings] 'Downloadable Assets' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|523 col 166| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-content.mdx|525 col 5| [Vale.Spelling] Did you really mean 'Repo'?
docs/vendor/enterprise-portal-v2-content.mdx|525 col 5| [Replicated.Headings] 'Repo Structure' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|537 col 202| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-content.mdx|537 col 227| [Replicated.Passive] In general, use active voice instead of passive voice ('are fetched').
docs/vendor/enterprise-portal-v2-content.mdx|537 col 262| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-content.mdx|539 col 5| [Replicated.Headings] 'Linking to Assets' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|549 col 58| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-content.mdx|551 col 44| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-content.mdx|553 col 5| [Replicated.Headings] 'Per-Customer Asset Delivery' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|576 col 36| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-content.mdx|578 col 128| [Vale.Spelling] Did you really mean 'PDFs'?
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|1 col 3| [Replicated.Headings] 'Versioned Docs (New)' should use sentence case.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|9 col 33| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|13 col 40| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|13 col 59| [Replicated.Passive] In general, use active voice instead of passive voice ('are discovered').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|15 col 12| [Replicated.Passive] In general, use active voice instead of passive voice ('is synced').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|15 col 62| [Replicated.Passive] In general, use active voice instead of passive voice ('is stored').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|16 col 136| [Vale.Spelling] Did you really mean 'semver'?
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|16 col 173| [Replicated.Passive] In general, use active voice instead of passive voice ('is shown').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|18 col 4| [Replicated.Headings] 'Version Dropdown' should use sentence case.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|22 col 10| [Replicated.Passive] In general, use active voice instead of passive voice ('are sorted').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|26 col 88| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|28 col 66| [Replicated.Passive] In general, use active voice instead of passive voice ('is resolved').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|30 col 4| [Replicated.Headings] 'Version Resolution' should use sentence case.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|34 col 104| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|35 col 149| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|36 col 85| [Vale.Spelling] Did you really mean 'semver'?
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|36 col 99| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|36 col 239| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|37 col 48| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|37 col 102| [Replicated.Passive] In general, use active voice instead of passive voice ('is served').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|39 col 133| [Replicated.Passive] In general, use active voice instead of passive voice ('are handled').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|41 col 4| [Replicated.Headings] 'Pinning Releases to Branches' should use sentence case.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|43 col 52| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'above'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|45 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|51 col 40| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'next to'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|53 col 1| [Replicated.Headings] 'Naming Your Branches ***********************' should use sentence case.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|55 col 202| [Replicated.Passive] In general, use active voice instead of passive voice ('are shown').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|57 col 153| [Replicated.Passive] In general, use active voice instead of passive voice ('is handled').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|59 col 67| [Replicated.Passive] In general, use active voice instead of passive voice ('are sorted').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|65 col 102| [Replicated.Passive] In general, use active voice instead of passive voice ('is skipped').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|65 col 130| [Replicated.Passive] In general, use active voice instead of passive voice ('are shown').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|68 col 4| [Replicated.Headings] 'Adding Versions' should use sentence case.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|76 col 4| [Replicated.Headings] 'Version Gating by Channel' should use sentence case.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|78 col 22| [Replicated.Passive] In general, use active voice instead of passive voice ('is filtered').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|80 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|80 col 148| [Replicated.Passive] In general, use active voice instead of passive voice ('is skipped').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|80 col 176| [Replicated.Passive] In general, use active voice instead of passive voice ('are shown').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|82 col 46| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|91 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|91 col 35| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|93 col 4| [Replicated.Headings] 'Removing Versions' should use sentence case.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|95 col 4| [Vale.Spelling] Did you really mean 'unpublish'?
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|101 col 1| [Replicated.Timeless] Avoid temporal words like 'Currently'.
docs/vendor/enterprise-portal-v2-terraform.mdx|1 col 3| [Replicated.Headings] 'Terraform Modules (New)' should use sentence case.
docs/vendor/enterprise-portal-v2-terraform.mdx|13 col 88| [Vale.Spelling] Did you really mean 'repo's'?
docs/vendor/enterprise-portal-v2-terraform.mdx|14 col 60| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-terraform.mdx|14 col 143| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-terraform.mdx|17 col 96| [Replicated.Passive] In general, use active voice instead of passive voice ('be enabled').
docs/vendor/enterprise-portal-v2-terraform.mdx|20 col 4| [Replicated.Headings] 'Enabling Terraform for Your App' should use sentence case.
docs/vendor/enterprise-portal-v2-terraform.mdx|25 col 79| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-terraform.mdx|25 col 168| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-terraform.mdx|27 col 4| [Replicated.Headings] 'Controlling Which Customers See Terraform Content' should use sentence case.
docs/vendor/enterprise-portal-v2-terraform.mdx|29 col 76| [Replicated.Passive] In general, use active voice instead of passive voice ('is controlled').
docs/vendor/enterprise-portal-v2-terraform.mdx|29 col 111| [Vale.Spelling] Did you really mean 'repo's'?
docs/vendor/enterprise-portal-v2-terraform.mdx|47 col 35| [Replicated.Timeless] Avoid temporal words like 'won't'.
docs/vendor/enterprise-portal-v2-terraform.mdx|49 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-terraform.mdx|49 col 42| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-terraform.mdx|49 col 72| [Replicated.Passive] In general, use active voice instead of passive voice ('is gated').
docs/vendor/enterprise-portal-v2-terraform.mdx|51 col 4| [Replicated.Headings] 'Module Reference Docs' should use sentence case.
docs/vendor/enterprise-portal-v2-terraform.mdx|53 col 45| [Vale.Spelling] Did you really mean 'repo's'?
docs/vendor/enterprise-portal-v2-terraform.mdx|79 col 53| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-terraform.mdx|79 col 104| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-terraform.mdx|84 col 46| [Replicated.Passive] In general, use active voice instead of passive voice ('are produced').
docs/vendor/enterprise-portal-v2-terraform.mdx|84 col 163| [Replicated.WordSwaps] Use 'after' or 'one time' instead of 'once'.
docs/vendor/enterprise-portal-v2-terraform.mdx|87 col 4| [Replicated.Headings] 'Proxy Registry' should use sentence case.
docs/vendor/enterprise-portal-v2-terraform.mdx|89 col 110| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-terraform.mdx|91 col 1| [Replicated.Headings] 'Vendor Setup (One-Time) ***************' should use sentence case.
docs/vendor/enterprise-portal-v2-terraform.mdx|95 col 39| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-terraform.mdx|95 col 106| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-terraform.mdx|95 col 139| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-terraform.mdx|95 col 144| [Replicated.Passive] In general, use active voice instead of passive voice ('is included').
docs/vendor/enterprise-portal-v2-terraform.mdx|95 col 169| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-terraform.mdx|97 col 30| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-terraform.mdx|99 col 27| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'next to'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-terraform.mdx|99 col 117| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-terraform.mdx|102 col 35| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-terraform.mdx|105 col 24| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-terraform.mdx|105 col 47| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-terraform.mdx|105 col 72| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-terraform.mdx|105 col 133| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-terraform.mdx|105 col 168| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-terraform.mdx|105 col 254| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-terraform.mdx|108 col 50| [Replicated.Passive] In general, use active voice instead of passive voice ('is driven').
docs/vendor/enterprise-portal-v2-terraform.mdx|108 col 82| [Vale.Spelling] Did you really mean 'URIs'?
docs/vendor/enterprise-portal-v2-terraform.mdx|108 col 103| [Vale.Spelling] Did you really mean 'repo's'?
docs/vendor/enterprise-portal-v2-terraform.mdx|108 col 126| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'above'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-terraform.mdx|108 col 153| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-terraform.mdx|116 col 149| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-terraform.mdx|119 col 5| [Replicated.Headings] 'Customer Setup (One-Time)' should use sentence case.
docs/vendor/enterprise-portal-v2-terraform.mdx|139 col 42| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-terraform.mdx|141 col 5| [Replicated.Headings] 'How It Works' should use sentence case.
docs/vendor/enterprise-portal-v2-terraform.mdx|146 col 185| [Replicated.Passive] In general, use active voice instead of passive voice ('are returned').
docs/vendor/enterprise-portal-v2-terraform.mdx|147 col 114| [Replicated.Acronyms] Spell out 'JWT' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-terraform.mdx|147 col 205| [Replicated.Acronyms] Spell out 'JWT' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-terraform.mdx|147 col 235| [Replicated.Acronyms] Spell out 'JWT' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-terraform.mdx|147 col 294| [Replicated.Passive] In general, use active voice instead of passive voice ('is stored').
docs/vendor/enterprise-portal-v2-terraform.mdx|148 col 47| [Replicated.Acronyms] Spell out 'JWT' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-terraform.mdx|150 col 47| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-terraform.mdx|152 col 5| [Replicated.Headings] 'Version Gating' should use sentence case.
docs/vendor/enterprise-portal-v2-terraform.mdx|154 col 10| [Replicated.Passive] In general, use active voice instead of passive voice ('are gated').
docs/vendor/enterprise-portal-v2-terraform.mdx|157 col 22| [Replicated.Passive] In general, use active voice instead of passive voice ('is assigned').
docs/vendor/enterprise-portal-v2-terraform.mdx|161 col 5| [Replicated.Headings] 'Current Limitations' should use sentence case.
docs/vendor/enterprise-portal-v2-terraform.mdx|165 col 63| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-terraform.mdx|166 col 17| [Replicated.Passive] In general, use active voice instead of passive voice ('is supported').
docs/vendor/enterprise-portal-v2-use.mdx|1 col 3| [Replicated.Headings] 'Log in to and Use the Enterprise Portal (New)' should use sentence case.
docs/vendor/enterprise-portal-v2-use.mdx|15 col 126| [Replicated.Passive] In general, use active voice instead of passive voice ('is sent').
docs/vendor/enterprise-portal-v2-use.mdx|15 col 162| [Replicated.Passive] In general, use active voice instead of passive voice ('is needed').
docs/vendor/enterprise-portal-v2-use.mdx|17 col 3| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-use.mdx|17 col 274| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-use.mdx|19 col 3| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-use.mdx|21 col 33| [Replicated.Passive] In general, use active voice instead of passive voice ('is configured').
docs/vendor/enterprise-portal-v2-use.mdx|21 col 175| [Replicated.Passive] In general, use active voice instead of passive voice ('are provisioned').
docs/vendor/enterprise-portal-v2-use.mdx|23 col 4| [Replicated.Headings] 'Portal Navigation' should use sentence case.
docs/vendor/enterprise-portal-v2-use.mdx|36 col 25| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-use.mdx|38 col 4| [Replicated.Headings] 'Installing and Upgrading' should use sentence case.
docs/vendor/enterprise-portal-v2-use.mdx|45 col 55| [Replicated.WordsToAvoid] Avoid using the word 'easy'.
docs/vendor/enterprise-portal-v2-use.mdx|47 col 22| [Replicated.Passive] In general, use active voice instead of passive voice ('are personalized').
docs/vendor/enterprise-portal-v2-use.mdx|57 col 4| [Replicated.Headings] 'Team Management' should use sentence case.
docs/vendor/enterprise-portal-v2-use.mdx|64 col 37| [Replicated.Passive] In general, use active voice instead of passive voice ('is enabled').
docs/vendor/enterprise-portal-v2-use.mdx|66 col 4| [Replicated.Headings] 'Support Bundles' should use sentence case.
docs/vendor/enterprise-portal-v2-use.mdx|76 col 208| [Replicated.Passive] In general, use active voice instead of passive voice ('is read').
docs/vendor/enterprise-portal-v2-use.mdx|80 col 5| [Replicated.Headings] 'Repository Not Showing in Dropdown' should use sentence case.
docs/vendor/enterprise-portal-v2-use.mdx|82 col 66| [Vale.Spelling] Did you really mean 'repos'?
docs/vendor/enterprise-portal-v2-use.mdx|84 col 5| [Replicated.Headings] 'Changes Not Appearing' should use sentence case.
docs/vendor/enterprise-portal-v2-use.mdx|97 col 5| [Replicated.Headings] 'Pages Not Showing in Navigation' should use sentence case.
docs/vendor/enterprise-portal-v2-use.mdx|102 col 9| [Vale.Spelling] Did you really mean 'frontmatter'?
docs/vendor/enterprise-portal-v2-use.mdx|105 col 5| [Replicated.Headings] 'Version Branch Not Working' should use sentence case.
docs/vendor/enterprise-portal-v2-use.mdx|111 col 5| [Replicated.Headings] 'Helm Chart Reference Docs Not Generating' should use sentence case.
docs/vendor/enterprise-portal-v2-use.mdx|115 col 108| [Replicated.Passive] In general, use active voice instead of passive voice ('is skipped').
docs/vendor/enterprise-portal-v2-use.mdx|118 col 5| [Replicated.Headings] 'Terraform Module Docs Not Loading' should use sentence case.
docs/vendor/enterprise-portal-v2-use.mdx|120 col 31| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-use.mdx|121 col 56| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-use.mdx|125 col 5| [Replicated.Headings] 'Terraform Proxy Registry Not Working' should use sentence case.
docs/vendor/enterprise-portal-v2-use.mdx|127 col 25| [Replicated.Passive] In general, use active voice instead of passive voice ('is installed').
docs/vendor/enterprise-portal-v2-use.mdx|127 col 70| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-use.mdx|128 col 25| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-use.mdx|128 col 30| [Replicated.Passive] In general, use active voice instead of passive voice ('is linked').
docs/vendor/enterprise-portal-v2-use.mdx|128 col 60| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-use.mdx|128 col 82| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-use.mdx|132 col 17| [Replicated.Passive] In general, use active voice instead of passive voice ('is supported').
docs/vendor/enterprise-portal-v2-use.mdx|134 col 5| [Replicated.Headings] 'Security Center Not Showing' should use sentence case.
docs/vendor/enterprise-portal-v2-use.mdx|136 col 74| [Replicated.Passive] In general, use active voice instead of passive voice ('is enabled').
docs/vendor/enterprise-portal-v2-use.mdx|138 col 28| [Replicated.Passive] In general, use active voice instead of passive voice ('is included').
docs/vendor/enterprise-portal-v2-use.mdx|139 col 17| [Replicated.Passive] In general, use active voice instead of passive voice ('is generated').
docs/vendor/enterprise-portal-v2-use.mdx|139 col 70| [Replicated.Passive] In general, use active voice instead of passive voice ('been promoted').
docs/vendor/enterprise-portal-v2-use.mdx|141 col 5| [Replicated.Headings] 'Customer Not Seeing New Portal' should use sentence case.
docs/vendor/enterprise-portal-v2-use.mdx|143 col 45| [Replicated.Passive] In general, use active voice instead of passive voice ('is set').
docs/vendor/enterprise-portal-v2-use.mdx|144 col 37| [Replicated.Passive] In general, use active voice instead of passive voice ('is deployed').
docs/vendor/enterprise-portal-v2-use.mdx|144 col 92| [Vale.Spelling] Did you really mean 'repo'?
docs/vendor/enterprise-portal-v2-use.mdx|145 col 41| [Replicated.Passive] In general, use active voice instead of passive voice ('is pointed').
docs/vendor/enterprise-portal-v2-use.mdx|147 col 5| [Replicated.Headings] 'Customer Invitation Not Received' should use sentence case.
docs/vendor/enterprise-portal-v2-use.mdx|151 col 75| [Replicated.Acronyms] Spell out 'DKIM' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-use.mdx|151 col 108| [Replicated.Passive] In general, use active voice instead of passive voice ('are verified').
docs/vendor/enterprise-portal-v2-use.mdx|152 col 78| [Replicated.Passive] In general, use active voice instead of passive voice ('be prompted').
docs/vendor/enterprise-portal-v2-use.mdx|154 col 5| [Replicated.Headings] 'Self-Service Signup Not Working' should use sentence case.
docs/vendor/enterprise-portal-v2-use.mdx|156 col 33| [Replicated.Passive] In general, use active voice instead of passive voice ('are enabled').
docs/vendor/enterprise-portal-v2-use.mdx|157 col 64| [Replicated.Passive] In general, use active voice instead of passive voice ('being shared').
docs/vendor/enterprise-portal-v2-use.mdx|159 col 5| [Replicated.Headings] 'Login Footer Showing Replicated Branding' should use sentence case.
docs/vendor/enterprise-portal-v2-use.mdx|162 col 76| [Replicated.Passive] In general, use active voice instead of passive voice ('is recommended').

github-actions · 2026-05-14T18:39:15Z

@@ -1,6 +1,10 @@
-# View a customer's Enterprise Portal
+# View a Customer's Enterprise Portal (Classic)


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.Headings] 'View a Customer's Enterprise Portal (Classic)' should use sentence case.

github-actions · 2026-05-14T18:39:15Z

+# View a Customer's Enterprise Portal (Classic)

-This topic describes how you can log in to the Enterprise Portal for a customer from the Vendor Portal. This is useful when testing your application installation and upgrade instructions, previewing customizations that you made to the Enterprise Portal, or managing Enterprise Portal users on behalf of one of your customers.
+This topic describes how you can log in to the Enterprise Portal (Classic) for a customer from the Vendor Portal. This is useful when testing your application installation and upgrade instructions, previewing customizations that you made to the Enterprise Portal, or managing Enterprise Portal users on behalf of one of your customers.


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.

github-actions · 2026-05-14T18:39:15Z

@@ -1,6 +1,10 @@
-# About the Enterprise Portal
+# About the Enterprise Portal (Classic)


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.Headings] 'About the Enterprise Portal (Classic)' should use sentence case.

github-actions · 2026-05-14T18:39:15Z

@@ -1,6 +1,10 @@
-# Enable self-service sign-ups
+# Enable Self-Service Sign-Ups (Classic)


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.Headings] 'Enable Self-Service Sign-Ups (Classic)' should use sentence case.

github-actions · 2026-05-14T18:39:15Z

@@ -0,0 +1,66 @@
+# About the Enterprise Portal (New)


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.Headings] 'About the Enterprise Portal (New)' should use sentence case.

github-actions · 2026-05-14T18:39:16Z

+
+### Vendor Portal View vs. Customer Portal Version
+
+The **New Portal** / **Classic Portal** toggle at the top of the Enterprise Portal page in Vendor Portal controls which view *you* see as a vendor. It does not change which portal your customers see. Customer portal versions are controlled individually via the Portal Version toggle on each customer's EP access tab.


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.

github-actions · 2026-05-14T18:39:16Z

@@ -1,6 +1,10 @@
-# Manage Enterprise Portal customer access
+# Manage Enterprise Portal Customer Access (Classic)


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.Headings] 'Manage Enterprise Portal Customer Access (Classic)' should use sentence case.

github-actions · 2026-05-14T18:39:16Z

@@ -0,0 +1,27 @@
+# View a Customer's Enterprise Portal (New)


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.Headings] 'View a Customer's Enterprise Portal (New)' should use sentence case.

github-actions · 2026-05-14T18:39:16Z

+
+For information about how end users can sign up for an account and log in to the Enterprise Portal, see [Log in to and Use the Enterprise Portal (New)](/vendor/enterprise-portal-v2-use).
+
+## Login as Customer


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.Headings] 'Login as Customer' should use sentence case.

github-actions · 2026-05-14T18:39:16Z

+
+The login routes to the correct portal version automatically. If the customer is on the new Enterprise Portal, the link opens `{appSlug}.enterpriseportal.app` (or your custom domain). If the customer is on Classic, the link opens `get.replicated.com`.
+
+## Local CLI Preview


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.Headings] 'Local CLI Preview' should use sentence case.

- Convert all v2 doc headings to sentence case to match v1 style - Add tech terms to vale accept list: repo, semver, frontmatter, callout, signups, enum, unpublish, PDFs, URIs Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

github-actions

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

vale

docs/vendor/enterprise-portal-v2-preview.mdx|38 col 220| [Replicated.Passive] In general, use active voice instead of passive voice ('be committed').
docs/vendor/enterprise-portal-v2-invite.mdx|1 col 3| [Replicated.Headings] 'Manage Customer Access (New)' should use sentence case.
docs/vendor/enterprise-portal-v2-invite.mdx|11 col 88| [Replicated.Passive] In general, use active voice instead of passive voice ('is controlled').
docs/vendor/enterprise-portal-v2-invite.mdx|17 col 133| [Replicated.Passive] In general, use active voice instead of passive voice ('is needed').
docs/vendor/enterprise-portal-v2-invite.mdx|35 col 67| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'next to'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-invite.mdx|40 col 34| [Replicated.Passive] In general, use active voice instead of passive voice ('be invited').
docs/vendor/enterprise-portal-v2-invite.mdx|46 col 64| [Replicated.Passive] In general, use active voice instead of passive voice ('be invited').
docs/vendor/enterprise-portal-v2-invite.mdx|48 col 4| [Replicated.Headings] 'SAML authentication (Alpha)' should use sentence case.
docs/vendor/enterprise-portal-v2-invite.mdx|56 col 67| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-invite.mdx|62 col 87| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'under'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-invite.mdx|63 col 20| [Replicated.Passive] In general, use active voice instead of passive voice ('are created').
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|1 col 3| [Replicated.Headings] 'Enable Self-Service Sign-Ups (New)' should use sentence case.
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|13 col 52| [Replicated.Passive] In general, use active voice instead of passive voice ('is assigned').
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|16 col 54| [Replicated.Passive] In general, use active voice instead of passive voice ('are enabled').
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|20 col 35| [Replicated.Passive] In general, use active voice instead of passive voice ('is generated').
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|30 col 52| [Replicated.Passive] In general, use active voice instead of passive voice ('be filled').
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|32 col 12| [Replicated.Passive] In general, use active voice instead of passive voice ('is assigned').
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|39 col 21| [Replicated.Passive] In general, use active voice instead of passive voice ('are configured').
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|40 col 26| [Replicated.Passive] In general, use active voice instead of passive voice ('are configured').
docs/vendor/enterprise-portal-v2-self-serve-signup.mdx|42 col 56| [Replicated.Passive] In general, use active voice instead of passive voice ('is activated').
docs/vendor/enterprise-portal-configure.mdx|1 col 3| [Replicated.Headings] 'Customize the Enterprise Portal (Classic)' should use sentence case.
docs/vendor/enterprise-portal-configure.mdx|3 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-use.mdx|1 col 3| [Replicated.Headings] 'Log in to and Use the Enterprise Portal (Classic)' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|1 col 3| [Replicated.Headings] 'Customize Portal Content (New)' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|7 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-content.mdx|105 col 83| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-content.mdx|111 col 1| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'Here'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-content.mdx|257 col 170| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-content.mdx|274 col 34| [Replicated.Passive] In general, use active voice instead of passive voice ('are personalized').
docs/vendor/enterprise-portal-v2-content.mdx|346 col 75| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-content.mdx|347 col 75| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'above'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-content.mdx|348 col 76| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-content.mdx|351 col 91| [Replicated.Passive] In general, use active voice instead of passive voice ('is stripped').
docs/vendor/enterprise-portal-v2-content.mdx|353 col 11| [Replicated.Passive] In general, use active voice instead of passive voice ('be combined').
docs/vendor/enterprise-portal-v2-content.mdx|353 col 50| [Replicated.Acronyms] Spell out 'AND' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-content.mdx|353 col 124| [Replicated.Passive] In general, use active voice instead of passive voice ('be parsed').
docs/vendor/enterprise-portal-v2-content.mdx|353 col 147| [Replicated.Passive] In general, use active voice instead of passive voice ('is hidden').
docs/vendor/enterprise-portal-v2-content.mdx|436 col 4| [Replicated.Headings] 'High Availability Setup' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|451 col 4| [Replicated.Headings] 'Acme-Specific Configuration' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|474 col 4| [Replicated.Headings] 'High Availability Setup' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|519 col 81| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-content.mdx|519 col 229| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-content.mdx|525 col 5| [Replicated.Headings] 'Repo structure' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|537 col 202| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-content.mdx|537 col 227| [Replicated.Passive] In general, use active voice instead of passive voice ('are fetched').
docs/vendor/enterprise-portal-v2-content.mdx|549 col 58| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-terraform.mdx|1 col 3| [Replicated.Headings] 'Terraform Modules (New)' should use sentence case.
docs/vendor/enterprise-portal-v2-terraform.mdx|14 col 60| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-terraform.mdx|17 col 96| [Replicated.Passive] In general, use active voice instead of passive voice ('be enabled').
docs/vendor/enterprise-portal-v2-terraform.mdx|25 col 168| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-terraform.mdx|29 col 76| [Replicated.Passive] In general, use active voice instead of passive voice ('is controlled').
docs/vendor/enterprise-portal-v2-terraform.mdx|47 col 35| [Replicated.Timeless] Avoid temporal words like 'won't'.
docs/vendor/enterprise-portal-v2-terraform.mdx|49 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-terraform.mdx|49 col 42| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-terraform.mdx|49 col 72| [Replicated.Passive] In general, use active voice instead of passive voice ('is gated').
docs/vendor/enterprise-portal-v2-terraform.mdx|84 col 46| [Replicated.Passive] In general, use active voice instead of passive voice ('are produced').
docs/vendor/enterprise-portal-v2-terraform.mdx|84 col 163| [Replicated.WordSwaps] Use 'after' or 'one time' instead of 'once'.
docs/vendor/enterprise-portal-v2-terraform.mdx|89 col 110| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-terraform.mdx|95 col 144| [Replicated.Passive] In general, use active voice instead of passive voice ('is included').
docs/vendor/enterprise-portal-v2-terraform.mdx|99 col 27| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'next to'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-terraform.mdx|105 col 168| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-terraform.mdx|105 col 254| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-terraform.mdx|108 col 50| [Replicated.Passive] In general, use active voice instead of passive voice ('is driven').
docs/vendor/enterprise-portal-v2-terraform.mdx|108 col 126| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'above'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-terraform.mdx|146 col 185| [Replicated.Passive] In general, use active voice instead of passive voice ('are returned').
docs/vendor/enterprise-portal-v2-terraform.mdx|147 col 114| [Replicated.Acronyms] Spell out 'JWT' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-terraform.mdx|147 col 205| [Replicated.Acronyms] Spell out 'JWT' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-terraform.mdx|147 col 235| [Replicated.Acronyms] Spell out 'JWT' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-terraform.mdx|147 col 294| [Replicated.Passive] In general, use active voice instead of passive voice ('is stored').
docs/vendor/enterprise-portal-v2-terraform.mdx|148 col 47| [Replicated.Acronyms] Spell out 'JWT' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-terraform.mdx|154 col 10| [Replicated.Passive] In general, use active voice instead of passive voice ('are gated').
docs/vendor/enterprise-portal-v2-terraform.mdx|157 col 22| [Replicated.Passive] In general, use active voice instead of passive voice ('is assigned').
docs/vendor/enterprise-portal-v2-terraform.mdx|166 col 17| [Replicated.Passive] In general, use active voice instead of passive voice ('is supported').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|1 col 3| [Replicated.Headings] 'Versioned Docs (New)' should use sentence case.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|13 col 59| [Replicated.Passive] In general, use active voice instead of passive voice ('are discovered').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|15 col 12| [Replicated.Passive] In general, use active voice instead of passive voice ('is synced').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|15 col 62| [Replicated.Passive] In general, use active voice instead of passive voice ('is stored').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|16 col 173| [Replicated.Passive] In general, use active voice instead of passive voice ('is shown').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|22 col 10| [Replicated.Passive] In general, use active voice instead of passive voice ('are sorted').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|26 col 88| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|28 col 66| [Replicated.Passive] In general, use active voice instead of passive voice ('is resolved').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|34 col 104| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|35 col 149| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|36 col 99| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|36 col 239| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|37 col 48| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|37 col 102| [Replicated.Passive] In general, use active voice instead of passive voice ('is served').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|39 col 133| [Replicated.Passive] In general, use active voice instead of passive voice ('are handled').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|43 col 52| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'above'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|45 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|51 col 40| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'next to'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|55 col 202| [Replicated.Passive] In general, use active voice instead of passive voice ('are shown').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|57 col 153| [Replicated.Passive] In general, use active voice instead of passive voice ('is handled').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|59 col 67| [Replicated.Passive] In general, use active voice instead of passive voice ('are sorted').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|65 col 102| [Replicated.Passive] In general, use active voice instead of passive voice ('is skipped').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|65 col 130| [Replicated.Passive] In general, use active voice instead of passive voice ('are shown').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|78 col 22| [Replicated.Passive] In general, use active voice instead of passive voice ('is filtered').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|80 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|80 col 148| [Replicated.Passive] In general, use active voice instead of passive voice ('is skipped').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|80 col 176| [Replicated.Passive] In general, use active voice instead of passive voice ('are shown').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|91 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|91 col 35| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|101 col 1| [Replicated.Timeless] Avoid temporal words like 'Currently'.
docs/vendor/enterprise-portal-v2-use.mdx|1 col 3| [Replicated.Headings] 'Log in to and Use the Enterprise Portal (New)' should use sentence case.
docs/vendor/enterprise-portal-v2-use.mdx|15 col 126| [Replicated.Passive] In general, use active voice instead of passive voice ('is sent').
docs/vendor/enterprise-portal-v2-use.mdx|15 col 162| [Replicated.Passive] In general, use active voice instead of passive voice ('is needed').
docs/vendor/enterprise-portal-v2-use.mdx|17 col 3| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-use.mdx|17 col 274| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-use.mdx|19 col 3| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-use.mdx|21 col 33| [Replicated.Passive] In general, use active voice instead of passive voice ('is configured').
docs/vendor/enterprise-portal-v2-use.mdx|21 col 175| [Replicated.Passive] In general, use active voice instead of passive voice ('are provisioned').
docs/vendor/enterprise-portal-v2-use.mdx|36 col 25| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-use.mdx|45 col 55| [Replicated.WordsToAvoid] Avoid using the word 'easy'.
docs/vendor/enterprise-portal-v2-use.mdx|47 col 22| [Replicated.Passive] In general, use active voice instead of passive voice ('are personalized').
docs/vendor/enterprise-portal-v2-use.mdx|64 col 37| [Replicated.Passive] In general, use active voice instead of passive voice ('is enabled').
docs/vendor/enterprise-portal-v2-use.mdx|76 col 208| [Replicated.Passive] In general, use active voice instead of passive voice ('is read').
docs/vendor/enterprise-portal-v2-use.mdx|115 col 108| [Replicated.Passive] In general, use active voice instead of passive voice ('is skipped').
docs/vendor/enterprise-portal-v2-use.mdx|127 col 25| [Replicated.Passive] In general, use active voice instead of passive voice ('is installed').
docs/vendor/enterprise-portal-v2-use.mdx|128 col 30| [Replicated.Passive] In general, use active voice instead of passive voice ('is linked').
docs/vendor/enterprise-portal-v2-use.mdx|132 col 17| [Replicated.Passive] In general, use active voice instead of passive voice ('is supported').
docs/vendor/enterprise-portal-v2-use.mdx|136 col 74| [Replicated.Passive] In general, use active voice instead of passive voice ('is enabled').
docs/vendor/enterprise-portal-v2-use.mdx|138 col 28| [Replicated.Passive] In general, use active voice instead of passive voice ('is included').
docs/vendor/enterprise-portal-v2-use.mdx|139 col 17| [Replicated.Passive] In general, use active voice instead of passive voice ('is generated').
docs/vendor/enterprise-portal-v2-use.mdx|139 col 70| [Replicated.Passive] In general, use active voice instead of passive voice ('been promoted').
docs/vendor/enterprise-portal-v2-use.mdx|143 col 45| [Replicated.Passive] In general, use active voice instead of passive voice ('is set').
docs/vendor/enterprise-portal-v2-use.mdx|144 col 37| [Replicated.Passive] In general, use active voice instead of passive voice ('is deployed').
docs/vendor/enterprise-portal-v2-use.mdx|145 col 41| [Replicated.Passive] In general, use active voice instead of passive voice ('is pointed').
docs/vendor/enterprise-portal-v2-use.mdx|151 col 75| [Replicated.Acronyms] Spell out 'DKIM' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-use.mdx|151 col 108| [Replicated.Passive] In general, use active voice instead of passive voice ('are verified').
docs/vendor/enterprise-portal-v2-use.mdx|152 col 78| [Replicated.Passive] In general, use active voice instead of passive voice ('be prompted').
docs/vendor/enterprise-portal-v2-use.mdx|156 col 33| [Replicated.Passive] In general, use active voice instead of passive voice ('are enabled').
docs/vendor/enterprise-portal-v2-use.mdx|157 col 64| [Replicated.Passive] In general, use active voice instead of passive voice ('being shared').
docs/vendor/enterprise-portal-v2-use.mdx|162 col 76| [Replicated.Passive] In general, use active voice instead of passive voice ('is recommended').

github-actions · 2026-05-14T19:02:52Z

@@ -0,0 +1,57 @@
+# Connect a Git Repo (New)


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.Headings] 'Connect a Git Repo (New)' should use sentence case.

github-actions · 2026-05-14T19:02:52Z

+Features described on this page are in alpha and subject to change. For access, contact your Replicated account representative.
+:::
+
+Enterprise Portal content is driven by a GitHub repo you control. Connecting a repo is a prerequisite to offer versioned docs, advanced theming, and Terraform module delivery.


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.Passive] In general, use active voice instead of passive voice ('is driven').

github-actions · 2026-05-14T19:02:52Z

+Go to **Enterprise Portal** in Vendor Portal. The **Content** tab is the default landing page. Click **Connect GitHub** and authorize the Replicated GitHub App on your GitHub organization.
+
+:::tip
+When installing the Replicated GitHub App, grant access to all repositories you plan to use with Enterprise Portal (content repos AND Terraform module repos). If you need to add access to additional repos later, update the GitHub App's repository permissions in your GitHub org settings (Settings > Integrations > Applications > Replicated > Configure > Repository access).


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.Acronyms] Spell out 'AND' on first use, if it's unfamiliar to the audience.

github-actions · 2026-05-14T19:02:52Z

+Go to **Enterprise Portal** in Vendor Portal. The **Content** tab is the default landing page. Click **Connect GitHub** and authorize the Replicated GitHub App on your GitHub organization.
+
+:::tip
+When installing the Replicated GitHub App, grant access to all repositories you plan to use with Enterprise Portal (content repos AND Terraform module repos). If you need to add access to additional repos later, update the GitHub App's repository permissions in your GitHub org settings (Settings > Integrations > Applications > Replicated > Configure > Repository access).


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.

github-actions · 2026-05-14T19:02:53Z

+Select your GitHub organization and the repository containing your Enterprise Portal content, then click **Link Repository**. When only one GitHub organization or repository is available, it is auto-selected for you.
+
+:::note
+The selected repository must contain a `toc.yaml` file at the root of its default branch. If none is found, you'll see a warning and won't be able to link the repo. Use the content template (Step 2) or add a `toc.yaml` manually before linking.


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.Passive] In general, use active voice instead of passive voice ('is found').

github-actions · 2026-05-14T19:02:53Z

@@ -0,0 +1,39 @@
+# Preview the Enterprise Portal (New)


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.Headings] 'Preview the Enterprise Portal (New)' should use sentence case.

github-actions · 2026-05-14T19:02:53Z

+Features described on this page are in alpha and subject to change. For access, contact your Replicated account representative.
+:::
+
+Before inviting any real customers, use Local Preview to see exactly what they'll experience.


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.Timeless] Avoid temporal words like 'they'll'.

github-actions · 2026-05-14T19:02:53Z

+replicated enterprise-portal preview /path/to/your-content-repo --app <your-app-slug>
+```
+
+The CLI pulls a preview container (first run only), starts a local server, and opens the full Enterprise Portal experience at `http://localhost:3000` (auto-increments if the port is busy).


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.

github-actions · 2026-05-14T19:02:53Z

+
+The CLI pulls a preview container (first run only), starts a local server, and opens the full Enterprise Portal experience at `http://localhost:3000` (auto-increments if the port is busy).
+
+If you are authenticated with the CLI (`replicated login`, `REPLICATED_API_TOKEN`, or `--token`), a customer switcher dropdown appears in the preview toolbar. Switching customers re-renders the page with that customer's entitlements, channel, and license data applied. Without a token, the preview runs with mock customer data.


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.Passive] In general, use active voice instead of passive voice ('are authenticated').

github-actions · 2026-05-14T19:02:54Z

+```
+
+:::note
+The local preview mocks market-api endpoints locally. Install flows, instance dashboards, and anything outside of docs content will render mostly empty or log benign errors. This is expected. Content changes must still be committed and pushed through your normal release flow to be visible to real customers.


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.Passive] In general, use active voice instead of passive voice ('is expected').

Docusaurus MDX v3 parses {{ }} as JSX expressions even inside backticks. Escape template syntax outside code fences with backslashes and add language tags to bare code blocks. Fix nested code fence in UpgradePath example by using four-backtick outer fence. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

github-actions

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

vale

docs/vendor/enterprise-portal-v2-terraform.mdx|49 col 42| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-terraform.mdx|49 col 72| [Replicated.Passive] In general, use active voice instead of passive voice ('is gated').
docs/vendor/enterprise-portal-v2-terraform.mdx|84 col 46| [Replicated.Passive] In general, use active voice instead of passive voice ('are produced').
docs/vendor/enterprise-portal-v2-terraform.mdx|84 col 163| [Replicated.WordSwaps] Use 'after' or 'one time' instead of 'once'.
docs/vendor/enterprise-portal-v2-terraform.mdx|89 col 110| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-terraform.mdx|95 col 144| [Replicated.Passive] In general, use active voice instead of passive voice ('is included').
docs/vendor/enterprise-portal-v2-terraform.mdx|99 col 27| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'next to'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-terraform.mdx|105 col 168| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-terraform.mdx|105 col 254| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-terraform.mdx|108 col 50| [Replicated.Passive] In general, use active voice instead of passive voice ('is driven').
docs/vendor/enterprise-portal-v2-terraform.mdx|108 col 126| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'above'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-terraform.mdx|146 col 185| [Replicated.Passive] In general, use active voice instead of passive voice ('are returned').
docs/vendor/enterprise-portal-v2-terraform.mdx|147 col 114| [Replicated.Acronyms] Spell out 'JWT' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-terraform.mdx|147 col 205| [Replicated.Acronyms] Spell out 'JWT' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-terraform.mdx|147 col 235| [Replicated.Acronyms] Spell out 'JWT' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-terraform.mdx|147 col 294| [Replicated.Passive] In general, use active voice instead of passive voice ('is stored').
docs/vendor/enterprise-portal-v2-terraform.mdx|148 col 47| [Replicated.Acronyms] Spell out 'JWT' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-terraform.mdx|154 col 10| [Replicated.Passive] In general, use active voice instead of passive voice ('are gated').
docs/vendor/enterprise-portal-v2-terraform.mdx|157 col 22| [Replicated.Passive] In general, use active voice instead of passive voice ('is assigned').
docs/vendor/enterprise-portal-v2-terraform.mdx|166 col 17| [Replicated.Passive] In general, use active voice instead of passive voice ('is supported').
docs/vendor/enterprise-portal-v2-content.mdx|1 col 3| [Replicated.Headings] 'Customize Portal Content (New)' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|7 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-content.mdx|105 col 83| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-content.mdx|111 col 1| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'Here'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-content.mdx|257 col 170| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-content.mdx|274 col 34| [Replicated.Passive] In general, use active voice instead of passive voice ('are personalized').
docs/vendor/enterprise-portal-v2-content.mdx|346 col 75| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-content.mdx|347 col 75| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'above'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-content.mdx|348 col 76| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-content.mdx|351 col 91| [Replicated.Passive] In general, use active voice instead of passive voice ('is stripped').
docs/vendor/enterprise-portal-v2-content.mdx|353 col 11| [Replicated.Passive] In general, use active voice instead of passive voice ('be combined').
docs/vendor/enterprise-portal-v2-content.mdx|353 col 50| [Replicated.Acronyms] Spell out 'AND' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-content.mdx|353 col 124| [Replicated.Passive] In general, use active voice instead of passive voice ('be parsed').
docs/vendor/enterprise-portal-v2-content.mdx|353 col 147| [Replicated.Passive] In general, use active voice instead of passive voice ('is hidden').
docs/vendor/enterprise-portal-v2-content.mdx|375 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-content.mdx|383 col 37| [Vale.Spelling] Did you really mean 'browsable'?
docs/vendor/enterprise-portal-v2-content.mdx|399 col 45| [Replicated.Passive] In general, use active voice instead of passive voice ('be enabled').
docs/vendor/enterprise-portal-v2-content.mdx|409 col 151| [Replicated.Passive] In general, use active voice instead of passive voice ('be used').
docs/vendor/enterprise-portal-v2-content.mdx|424 col 79| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-content.mdx|432 col 49| [Vale.Spelling] Did you really mean 'truthy'?
docs/vendor/enterprise-portal-v2-content.mdx|441 col 8| [Replicated.Passive] In general, use active voice instead of passive voice ('are considered').
docs/vendor/enterprise-portal-v2-content.mdx|441 col 23| [Vale.Spelling] Did you really mean 'falsy'?
docs/vendor/enterprise-portal-v2-content.mdx|441 col 115| [Vale.Spelling] Did you really mean 'truthy'?
docs/vendor/enterprise-portal-v2-content.mdx|456 col 27| [Replicated.Passive] In general, use active voice instead of passive voice ('be quoted').
docs/vendor/enterprise-portal-v2-content.mdx|462 col 42| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-content.mdx|481 col 86| [Replicated.Passive] In general, use active voice instead of passive voice ('be satisfied').
docs/vendor/enterprise-portal-v2-content.mdx|481 col 100| [Replicated.Acronyms] Spell out 'AND' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-content.mdx|519 col 81| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-content.mdx|519 col 229| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-content.mdx|525 col 5| [Replicated.Headings] 'Repo structure' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|537 col 202| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-content.mdx|537 col 227| [Replicated.Passive] In general, use active voice instead of passive voice ('are fetched').
docs/vendor/enterprise-portal-v2-content.mdx|549 col 58| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|1 col 3| [Replicated.Headings] 'Versioned Docs (New)' should use sentence case.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|13 col 59| [Replicated.Passive] In general, use active voice instead of passive voice ('are discovered').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|15 col 12| [Replicated.Passive] In general, use active voice instead of passive voice ('is synced').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|15 col 62| [Replicated.Passive] In general, use active voice instead of passive voice ('is stored').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|16 col 173| [Replicated.Passive] In general, use active voice instead of passive voice ('is shown').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|22 col 10| [Replicated.Passive] In general, use active voice instead of passive voice ('are sorted').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|26 col 88| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|28 col 66| [Replicated.Passive] In general, use active voice instead of passive voice ('is resolved').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|34 col 104| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|35 col 149| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|36 col 99| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|36 col 239| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|37 col 48| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|37 col 102| [Replicated.Passive] In general, use active voice instead of passive voice ('is served').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|39 col 133| [Replicated.Passive] In general, use active voice instead of passive voice ('are handled').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|43 col 52| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'above'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|45 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|51 col 40| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'next to'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|55 col 202| [Replicated.Passive] In general, use active voice instead of passive voice ('are shown').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|57 col 153| [Replicated.Passive] In general, use active voice instead of passive voice ('is handled').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|59 col 67| [Replicated.Passive] In general, use active voice instead of passive voice ('are sorted').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|65 col 102| [Replicated.Passive] In general, use active voice instead of passive voice ('is skipped').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|65 col 130| [Replicated.Passive] In general, use active voice instead of passive voice ('are shown').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|78 col 22| [Replicated.Passive] In general, use active voice instead of passive voice ('is filtered').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|80 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|80 col 148| [Replicated.Passive] In general, use active voice instead of passive voice ('is skipped').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|80 col 176| [Replicated.Passive] In general, use active voice instead of passive voice ('are shown').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|91 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|91 col 35| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|101 col 1| [Replicated.Timeless] Avoid temporal words like 'Currently'.
docs/vendor/enterprise-portal-v2-use.mdx|1 col 3| [Replicated.Headings] 'Log in to and Use the Enterprise Portal (New)' should use sentence case.
docs/vendor/enterprise-portal-v2-use.mdx|15 col 126| [Replicated.Passive] In general, use active voice instead of passive voice ('is sent').
docs/vendor/enterprise-portal-v2-use.mdx|15 col 162| [Replicated.Passive] In general, use active voice instead of passive voice ('is needed').
docs/vendor/enterprise-portal-v2-use.mdx|17 col 3| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-use.mdx|17 col 274| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-use.mdx|19 col 3| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-use.mdx|21 col 33| [Replicated.Passive] In general, use active voice instead of passive voice ('is configured').
docs/vendor/enterprise-portal-v2-use.mdx|21 col 175| [Replicated.Passive] In general, use active voice instead of passive voice ('are provisioned').
docs/vendor/enterprise-portal-v2-use.mdx|36 col 25| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-use.mdx|45 col 55| [Replicated.WordsToAvoid] Avoid using the word 'easy'.
docs/vendor/enterprise-portal-v2-use.mdx|47 col 22| [Replicated.Passive] In general, use active voice instead of passive voice ('are personalized').
docs/vendor/enterprise-portal-v2-use.mdx|64 col 37| [Replicated.Passive] In general, use active voice instead of passive voice ('is enabled').
docs/vendor/enterprise-portal-v2-use.mdx|76 col 208| [Replicated.Passive] In general, use active voice instead of passive voice ('is read').
docs/vendor/enterprise-portal-v2-use.mdx|115 col 108| [Replicated.Passive] In general, use active voice instead of passive voice ('is skipped').
docs/vendor/enterprise-portal-v2-use.mdx|127 col 25| [Replicated.Passive] In general, use active voice instead of passive voice ('is installed').
docs/vendor/enterprise-portal-v2-use.mdx|128 col 30| [Replicated.Passive] In general, use active voice instead of passive voice ('is linked').
docs/vendor/enterprise-portal-v2-use.mdx|132 col 17| [Replicated.Passive] In general, use active voice instead of passive voice ('is supported').
docs/vendor/enterprise-portal-v2-use.mdx|136 col 74| [Replicated.Passive] In general, use active voice instead of passive voice ('is enabled').
docs/vendor/enterprise-portal-v2-use.mdx|138 col 28| [Replicated.Passive] In general, use active voice instead of passive voice ('is included').
docs/vendor/enterprise-portal-v2-use.mdx|139 col 17| [Replicated.Passive] In general, use active voice instead of passive voice ('is generated').
docs/vendor/enterprise-portal-v2-use.mdx|139 col 70| [Replicated.Passive] In general, use active voice instead of passive voice ('been promoted').
docs/vendor/enterprise-portal-v2-use.mdx|143 col 45| [Replicated.Passive] In general, use active voice instead of passive voice ('is set').
docs/vendor/enterprise-portal-v2-use.mdx|144 col 37| [Replicated.Passive] In general, use active voice instead of passive voice ('is deployed').
docs/vendor/enterprise-portal-v2-use.mdx|145 col 41| [Replicated.Passive] In general, use active voice instead of passive voice ('is pointed').
docs/vendor/enterprise-portal-v2-use.mdx|151 col 75| [Replicated.Acronyms] Spell out 'DKIM' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-use.mdx|151 col 108| [Replicated.Passive] In general, use active voice instead of passive voice ('are verified').
docs/vendor/enterprise-portal-v2-use.mdx|152 col 78| [Replicated.Passive] In general, use active voice instead of passive voice ('be prompted').
docs/vendor/enterprise-portal-v2-use.mdx|156 col 33| [Replicated.Passive] In general, use active voice instead of passive voice ('are enabled').
docs/vendor/enterprise-portal-v2-use.mdx|157 col 64| [Replicated.Passive] In general, use active voice instead of passive voice ('being shared').
docs/vendor/enterprise-portal-v2-use.mdx|162 col 76| [Replicated.Passive] In general, use active voice instead of passive voice ('is recommended').

github-actions · 2026-05-14T20:17:08Z

@@ -1,6 +1,10 @@
-# Customize the Enterprise Portal
+# Customize the Enterprise Portal (Classic)


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.Headings] 'Customize the Enterprise Portal (Classic)' should use sentence case.

github-actions · 2026-05-14T20:17:08Z

+# Customize the Enterprise Portal (Classic)

-This topic describes how to customize the Enterprise Portal, including using a custom domain, changing the branding, editing the content of invitation and notification emails, and adding custom documentation.
+This topic describes how to customize the Enterprise Portal (Classic), including using a custom domain, changing the branding, editing the content of invitation and notification emails, and adding custom documentation.


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.

github-actions · 2026-05-14T20:17:08Z

+```
+
+:::note
+The local preview mocks market-api endpoints locally. Install flows, instance dashboards, and anything outside of docs content will render mostly empty or log benign errors. This is expected. Content changes must still be committed and pushed through your normal release flow to be visible to real customers.


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.Passive] In general, use active voice instead of passive voice ('be committed').

github-actions · 2026-05-14T20:17:08Z

@@ -0,0 +1,77 @@
+# Manage Customer Access (New)


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.Headings] 'Manage Customer Access (New)' should use sentence case.

github-actions · 2026-05-14T20:17:08Z

+
+## Enabling Enterprise Portal for customers
+
+For vendors using both Classic and New Enterprise Portal (mixed mode), customer access is controlled per-customer:


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.Passive] In general, use active voice instead of passive voice ('is controlled').

github-actions · 2026-05-14T20:17:09Z

+- **Proxy Registry**: Lets customers pull modules directly via `terraform init` using their license ID. Requires linking a separate Terraform repo and promoting releases with matching version labels.
+
+:::note
+Terraform module features require the `Terraform Modules in Enterprise Portal` feature flag to be enabled for your team. If you don't see the **Terraform** tab in Enterprise Portal, contact Replicated support to enable it.


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.Passive] In general, use active voice instead of passive voice ('be enabled').

github-actions · 2026-05-14T20:17:09Z

+Terraform features require two setup steps on the vendor side before customers see anything:
+
+1. **Feature flag enablement**: A Replicated admin enables the `Terraform Modules in Enterprise Portal` flag for your team. Contact Replicated support to request this.
+1. **Link a Terraform repository**: In the **Terraform** tab, link the GitHub repo containing your Terraform modules (see [Proxy Registry Vendor Setup](#vendor-setup) below).


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.

github-actions · 2026-05-14T20:17:09Z

+
+## Controlling which customers see Terraform content
+
+There is no built-in Terraform-specific license field. Customer visibility is controlled through your content repo's `visible_when` entitlements in `toc.yaml`. To gate Terraform content per customer:


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.Passive] In general, use active voice instead of passive voice ('is controlled').

github-actions · 2026-05-14T20:17:09Z

+          - isAWSEnabled
+```
+
+Customers without the entitlement won't see the navigation items or be able to access the module reference docs. You can combine multiple entitlements for more granular control (e.g., per-cloud-provider gating).


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.Timeless] Avoid temporal words like 'won't'.

github-actions · 2026-05-14T20:17:09Z

+
+Customers without the entitlement won't see the navigation items or be able to access the module reference docs. You can combine multiple entitlements for more granular control (e.g., per-cloud-provider gating).
+
+For the proxy registry (module downloads via `terraform init`), access is gated by the customer's license being active and on a channel with promoted releases containing matching version labels. There is no additional per-customer toggle needed for download access. If a customer has a valid license, they can pull any module version available on their channel.


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.

- Move troubleshooting section from the customer-facing "Use" page to its own "Troubleshoot the Enterprise Portal" page - Remove (Classic) and (New) from all page titles since the sidebar section headers already distinguish them - Switch Classic page callouts from :::tip to :::note to match existing docs conventions - Remove (New) from cross-reference link text - Add pending signup alert mention to self-service sign-ups page - Restore original Classic page titles (no parenthetical suffixes) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

github-actions

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

vale

docs/vendor/enterprise-portal-v2-content.mdx|462 col 42| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-content.mdx|481 col 86| [Replicated.Passive] In general, use active voice instead of passive voice ('be satisfied').
docs/vendor/enterprise-portal-v2-content.mdx|481 col 100| [Replicated.Acronyms] Spell out 'AND' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-content.mdx|519 col 81| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-content.mdx|519 col 229| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-content.mdx|525 col 5| [Replicated.Headings] 'Repo structure' should use sentence case.
docs/vendor/enterprise-portal-v2-content.mdx|537 col 202| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-content.mdx|537 col 227| [Replicated.Passive] In general, use active voice instead of passive voice ('are fetched').
docs/vendor/enterprise-portal-v2-content.mdx|549 col 58| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-use.mdx|15 col 126| [Replicated.Passive] In general, use active voice instead of passive voice ('is sent').
docs/vendor/enterprise-portal-v2-use.mdx|15 col 162| [Replicated.Passive] In general, use active voice instead of passive voice ('is needed').
docs/vendor/enterprise-portal-v2-use.mdx|17 col 3| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-use.mdx|17 col 274| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-use.mdx|19 col 3| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-use.mdx|21 col 33| [Replicated.Passive] In general, use active voice instead of passive voice ('is configured').
docs/vendor/enterprise-portal-v2-use.mdx|21 col 175| [Replicated.Passive] In general, use active voice instead of passive voice ('are provisioned').
docs/vendor/enterprise-portal-v2-use.mdx|36 col 25| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-use.mdx|45 col 55| [Replicated.WordsToAvoid] Avoid using the word 'easy'.
docs/vendor/enterprise-portal-v2-use.mdx|47 col 22| [Replicated.Passive] In general, use active voice instead of passive voice ('are personalized').
docs/vendor/enterprise-portal-v2-use.mdx|64 col 37| [Replicated.Passive] In general, use active voice instead of passive voice ('is enabled').
docs/vendor/enterprise-portal-v2-use.mdx|76 col 208| [Replicated.Passive] In general, use active voice instead of passive voice ('is read').
docs/vendor/enterprise-portal-v2-terraform.mdx|1 col 3| [Replicated.Headings] 'Terraform Modules' should use sentence case.
docs/vendor/enterprise-portal-v2-terraform.mdx|49 col 42| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-terraform.mdx|49 col 72| [Replicated.Passive] In general, use active voice instead of passive voice ('is gated').
docs/vendor/enterprise-portal-v2-terraform.mdx|84 col 46| [Replicated.Passive] In general, use active voice instead of passive voice ('are produced').
docs/vendor/enterprise-portal-v2-terraform.mdx|84 col 163| [Replicated.WordSwaps] Use 'after' or 'one time' instead of 'once'.
docs/vendor/enterprise-portal-v2-terraform.mdx|89 col 110| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-terraform.mdx|95 col 144| [Replicated.Passive] In general, use active voice instead of passive voice ('is included').
docs/vendor/enterprise-portal-v2-terraform.mdx|99 col 27| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'next to'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-terraform.mdx|105 col 168| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-terraform.mdx|105 col 254| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-terraform.mdx|108 col 50| [Replicated.Passive] In general, use active voice instead of passive voice ('is driven').
docs/vendor/enterprise-portal-v2-terraform.mdx|108 col 126| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'above'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-terraform.mdx|146 col 185| [Replicated.Passive] In general, use active voice instead of passive voice ('are returned').
docs/vendor/enterprise-portal-v2-terraform.mdx|147 col 114| [Replicated.Acronyms] Spell out 'JWT' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-terraform.mdx|147 col 205| [Replicated.Acronyms] Spell out 'JWT' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-terraform.mdx|147 col 235| [Replicated.Acronyms] Spell out 'JWT' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-terraform.mdx|147 col 294| [Replicated.Passive] In general, use active voice instead of passive voice ('is stored').
docs/vendor/enterprise-portal-v2-terraform.mdx|148 col 47| [Replicated.Acronyms] Spell out 'JWT' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-terraform.mdx|154 col 10| [Replicated.Passive] In general, use active voice instead of passive voice ('are gated').
docs/vendor/enterprise-portal-v2-terraform.mdx|157 col 22| [Replicated.Passive] In general, use active voice instead of passive voice ('is assigned').
docs/vendor/enterprise-portal-v2-terraform.mdx|166 col 17| [Replicated.Passive] In general, use active voice instead of passive voice ('is supported').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|44 col 108| [Replicated.Passive] In general, use active voice instead of passive voice ('is skipped').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|56 col 25| [Replicated.Passive] In general, use active voice instead of passive voice ('is installed').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|57 col 30| [Replicated.Passive] In general, use active voice instead of passive voice ('is linked').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|61 col 17| [Replicated.Passive] In general, use active voice instead of passive voice ('is supported').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|65 col 74| [Replicated.Passive] In general, use active voice instead of passive voice ('is enabled').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|67 col 28| [Replicated.Passive] In general, use active voice instead of passive voice ('is included').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|68 col 17| [Replicated.Passive] In general, use active voice instead of passive voice ('is generated').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|68 col 70| [Replicated.Passive] In general, use active voice instead of passive voice ('been promoted').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|72 col 45| [Replicated.Passive] In general, use active voice instead of passive voice ('is set').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|73 col 37| [Replicated.Passive] In general, use active voice instead of passive voice ('is deployed').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|74 col 41| [Replicated.Passive] In general, use active voice instead of passive voice ('is pointed').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|80 col 75| [Replicated.Acronyms] Spell out 'DKIM' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|80 col 108| [Replicated.Passive] In general, use active voice instead of passive voice ('are verified').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|81 col 78| [Replicated.Passive] In general, use active voice instead of passive voice ('be prompted').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|85 col 33| [Replicated.Passive] In general, use active voice instead of passive voice ('are enabled').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|86 col 64| [Replicated.Passive] In general, use active voice instead of passive voice ('being shared').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|91 col 76| [Replicated.Passive] In general, use active voice instead of passive voice ('is recommended').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|1 col 3| [Replicated.Headings] 'Versioned Docs' should use sentence case.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|13 col 59| [Replicated.Passive] In general, use active voice instead of passive voice ('are discovered').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|15 col 12| [Replicated.Passive] In general, use active voice instead of passive voice ('is synced').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|15 col 62| [Replicated.Passive] In general, use active voice instead of passive voice ('is stored').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|16 col 173| [Replicated.Passive] In general, use active voice instead of passive voice ('is shown').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|22 col 10| [Replicated.Passive] In general, use active voice instead of passive voice ('are sorted').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|26 col 88| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|28 col 66| [Replicated.Passive] In general, use active voice instead of passive voice ('is resolved').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|34 col 104| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|35 col 149| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|36 col 99| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|36 col 239| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|37 col 48| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|37 col 102| [Replicated.Passive] In general, use active voice instead of passive voice ('is served').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|39 col 133| [Replicated.Passive] In general, use active voice instead of passive voice ('are handled').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|43 col 52| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'above'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|45 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|51 col 40| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'next to'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|55 col 202| [Replicated.Passive] In general, use active voice instead of passive voice ('are shown').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|57 col 153| [Replicated.Passive] In general, use active voice instead of passive voice ('is handled').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|59 col 67| [Replicated.Passive] In general, use active voice instead of passive voice ('are sorted').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|65 col 102| [Replicated.Passive] In general, use active voice instead of passive voice ('is skipped').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|65 col 130| [Replicated.Passive] In general, use active voice instead of passive voice ('are shown').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|78 col 22| [Replicated.Passive] In general, use active voice instead of passive voice ('is filtered').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|80 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|80 col 148| [Replicated.Passive] In general, use active voice instead of passive voice ('is skipped').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|80 col 176| [Replicated.Passive] In general, use active voice instead of passive voice ('are shown').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|91 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|91 col 35| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|101 col 1| [Replicated.Timeless] Avoid temporal words like 'Currently'.

github-actions · 2026-05-14T20:32:54Z

@@ -0,0 +1,27 @@
+# View a Customer's Enterprise Portal


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.Headings] 'View a Customer's Enterprise Portal' should use sentence case.

github-actions · 2026-05-14T20:32:54Z

@@ -0,0 +1,80 @@
+# Customize Portal Branding


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.Headings] 'Customize Portal Branding' should use sentence case.

github-actions · 2026-05-14T20:32:54Z

@@ -0,0 +1,57 @@
+# Connect a Git Repo


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.Headings] 'Connect a Git Repo' should use sentence case.

github-actions · 2026-05-14T20:32:54Z

@@ -0,0 +1,57 @@
+# Helm Reference Docs


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.Headings] 'Helm Reference Docs' should use sentence case.

github-actions · 2026-05-14T20:32:54Z

@@ -0,0 +1,77 @@
+# Manage Customer Access


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.Headings] 'Manage Customer Access' should use sentence case.

github-actions · 2026-05-14T20:32:55Z

+
+### Conditionals
+
+**`\{\{#if\}\}`**: Show content when a value is truthy. Supports nesting.


🚫 [vale] _{reported by reviewdog 🐶}
[Vale.Spelling] Did you really mean 'truthy'?

github-actions · 2026-05-14T20:32:55Z

+{{/if}}
+```
+
+Values are considered falsy if they are null, empty string, `false`, `"false"`, `"0"`, or `0`. Everything else is truthy.


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.Passive] In general, use active voice instead of passive voice ('are considered').

github-actions · 2026-05-14T20:32:55Z

+{{/if}}
+```
+
+Values are considered falsy if they are null, empty string, `false`, `"false"`, `"0"`, or `0`. Everything else is truthy.


🚫 [vale] _{reported by reviewdog 🐶}
[Vale.Spelling] Did you really mean 'falsy'?

github-actions · 2026-05-14T20:32:55Z

+{{/if}}
+```
+
+Values are considered falsy if they are null, empty string, `false`, `"false"`, `"0"`, or `0`. Everything else is truthy.


🚫 [vale] _{reported by reviewdog 🐶}
[Vale.Spelling] Did you really mean 'truthy'?

github-actions · 2026-05-14T20:32:55Z

+{{/ifEquals}}
+```
+
+The comparison value must be quoted (double or single quotes). Supports nesting.


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.Passive] In general, use active voice instead of passive voice ('be quoted').

- Switch :::tip to :::note on connect repo page - Merge the two separate Terraform access notes into one - Replace "market-api" with "some backend endpoints" in preview note Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

github-actions

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

vale

docs/vendor/enterprise-portal-v2-terraform.mdx|153 col 22| [Replicated.Passive] In general, use active voice instead of passive voice ('is assigned').
docs/vendor/enterprise-portal-v2-terraform.mdx|162 col 17| [Replicated.Passive] In general, use active voice instead of passive voice ('is supported').
docs/vendor/enterprise-portal-v2-use.mdx|15 col 126| [Replicated.Passive] In general, use active voice instead of passive voice ('is sent').
docs/vendor/enterprise-portal-v2-use.mdx|15 col 162| [Replicated.Passive] In general, use active voice instead of passive voice ('is needed').
docs/vendor/enterprise-portal-v2-use.mdx|17 col 3| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-use.mdx|17 col 274| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-use.mdx|19 col 3| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-use.mdx|21 col 33| [Replicated.Passive] In general, use active voice instead of passive voice ('is configured').
docs/vendor/enterprise-portal-v2-use.mdx|21 col 175| [Replicated.Passive] In general, use active voice instead of passive voice ('are provisioned').
docs/vendor/enterprise-portal-v2-use.mdx|36 col 25| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-use.mdx|45 col 55| [Replicated.WordsToAvoid] Avoid using the word 'easy'.
docs/vendor/enterprise-portal-v2-use.mdx|47 col 22| [Replicated.Passive] In general, use active voice instead of passive voice ('are personalized').
docs/vendor/enterprise-portal-v2-use.mdx|64 col 37| [Replicated.Passive] In general, use active voice instead of passive voice ('is enabled').
docs/vendor/enterprise-portal-v2-use.mdx|76 col 208| [Replicated.Passive] In general, use active voice instead of passive voice ('is read').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|1 col 3| [Replicated.Headings] 'Versioned Docs' should use sentence case.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|13 col 59| [Replicated.Passive] In general, use active voice instead of passive voice ('are discovered').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|15 col 12| [Replicated.Passive] In general, use active voice instead of passive voice ('is synced').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|15 col 62| [Replicated.Passive] In general, use active voice instead of passive voice ('is stored').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|16 col 173| [Replicated.Passive] In general, use active voice instead of passive voice ('is shown').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|22 col 10| [Replicated.Passive] In general, use active voice instead of passive voice ('are sorted').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|26 col 88| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|28 col 66| [Replicated.Passive] In general, use active voice instead of passive voice ('is resolved').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|34 col 104| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|35 col 149| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|36 col 99| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|36 col 239| [Replicated.Passive] In general, use active voice instead of passive voice ('is used').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|37 col 48| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'below'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|37 col 102| [Replicated.Passive] In general, use active voice instead of passive voice ('is served').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|39 col 133| [Replicated.Passive] In general, use active voice instead of passive voice ('are handled').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|43 col 52| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'above'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|45 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|51 col 40| [Replicated.PositionalLanguage] Avoid spacial and directional language like 'next to'. Instead, use 'on this page', 'the following', or link to the section.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|55 col 202| [Replicated.Passive] In general, use active voice instead of passive voice ('are shown').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|57 col 153| [Replicated.Passive] In general, use active voice instead of passive voice ('is handled').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|59 col 67| [Replicated.Passive] In general, use active voice instead of passive voice ('are sorted').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|65 col 102| [Replicated.Passive] In general, use active voice instead of passive voice ('is skipped').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|65 col 130| [Replicated.Passive] In general, use active voice instead of passive voice ('are shown').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|78 col 22| [Replicated.Passive] In general, use active voice instead of passive voice ('is filtered').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|80 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|80 col 148| [Replicated.Passive] In general, use active voice instead of passive voice ('is skipped').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|80 col 176| [Replicated.Passive] In general, use active voice instead of passive voice ('are shown').
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|91 col 1| [Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|91 col 35| [Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.
docs/vendor/enterprise-portal-v2-versioned-docs.mdx|101 col 1| [Replicated.Timeless] Avoid temporal words like 'Currently'.
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|44 col 108| [Replicated.Passive] In general, use active voice instead of passive voice ('is skipped').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|56 col 25| [Replicated.Passive] In general, use active voice instead of passive voice ('is installed').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|57 col 30| [Replicated.Passive] In general, use active voice instead of passive voice ('is linked').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|61 col 17| [Replicated.Passive] In general, use active voice instead of passive voice ('is supported').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|65 col 74| [Replicated.Passive] In general, use active voice instead of passive voice ('is enabled').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|67 col 28| [Replicated.Passive] In general, use active voice instead of passive voice ('is included').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|68 col 17| [Replicated.Passive] In general, use active voice instead of passive voice ('is generated').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|68 col 70| [Replicated.Passive] In general, use active voice instead of passive voice ('been promoted').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|72 col 45| [Replicated.Passive] In general, use active voice instead of passive voice ('is set').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|73 col 37| [Replicated.Passive] In general, use active voice instead of passive voice ('is deployed').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|74 col 41| [Replicated.Passive] In general, use active voice instead of passive voice ('is pointed').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|80 col 75| [Replicated.Acronyms] Spell out 'DKIM' on first use, if it's unfamiliar to the audience.
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|80 col 108| [Replicated.Passive] In general, use active voice instead of passive voice ('are verified').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|81 col 78| [Replicated.Passive] In general, use active voice instead of passive voice ('be prompted').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|85 col 33| [Replicated.Passive] In general, use active voice instead of passive voice ('are enabled').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|86 col 64| [Replicated.Passive] In general, use active voice instead of passive voice ('being shared').
docs/vendor/enterprise-portal-v2-troubleshooting.mdx|91 col 76| [Replicated.Passive] In general, use active voice instead of passive voice ('is recommended').

github-actions · 2026-05-14T21:25:23Z

+```
+
+:::note
+The local preview mocks some backend endpoints locally. Install flows, instance dashboards, and anything outside of docs content will render mostly empty or log benign errors. This is expected. Content changes must still be committed and pushed through your normal release flow to be visible to real customers.


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.Passive] In general, use active voice instead of passive voice ('is expected').

github-actions · 2026-05-14T21:25:23Z

+```
+
+:::note
+The local preview mocks some backend endpoints locally. Install flows, instance dashboards, and anything outside of docs content will render mostly empty or log benign errors. This is expected. Content changes must still be committed and pushed through your normal release flow to be visible to real customers.


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.Passive] In general, use active voice instead of passive voice ('be committed').

github-actions · 2026-05-14T21:25:23Z

+
+Entitlements are accessible as `\{\{ entitlements.<name> \}\}` for interpolation and `\{\{#if entitlements.<name>\}\}` for conditionals. There are two kinds:
+
+- **Built-in flags**: Set on the license via Vendor Portal: `isHelmInstallEnabled`, `isAirgapSupported`, `isEmbeddedClusterDownloadEnabled`, `isEmbeddedClusterMultiNodeEnabled`, `isKotsInstallEnabled`, `isHelmAirgapEnabled`


⚠️ [vale] _{reported by reviewdog 🐶}
[Replicated.WordSwaps] Use 'with' or 'through' instead of 'via'.

github-actions · 2026-05-14T21:25:23Z

+
+## Visibility {#visibility}
+
+Use `visible_when` to control which customers see which content. All conditions must be satisfied (AND logic).


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.Passive] In general, use active voice instead of passive voice ('be satisfied').

github-actions · 2026-05-14T21:25:23Z

+
+## Visibility {#visibility}
+
+Use `visible_when` to control which customers see which content. All conditions must be satisfied (AND logic).


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.Acronyms] Spell out 'AND' on first use, if it's unfamiliar to the audience.

github-actions · 2026-05-14T21:25:24Z

+
+1. **Discovery**: Worker returns a static registry manifest pointing to the modules API. No auth required.
+1. **List versions**: Worker calls the Replicated API, which validates the license, checks the customer's channel, and returns the allowed `version_label` values. Only version numbers are returned to the customer.
+1. **Download pointer**: Worker calls the Replicated API to create a short-lived server-side session backed by a JWT. The response includes an `X-Terraform-Get` header with the archive URL containing the JWT as a query parameter. The JWT is an opaque, short-lived token. The GitHub credential is stored server-side and never exposed to the customer.


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.Acronyms] Spell out 'JWT' on first use, if it's unfamiliar to the audience.

github-actions · 2026-05-14T21:25:24Z

+
+1. **Discovery**: Worker returns a static registry manifest pointing to the modules API. No auth required.
+1. **List versions**: Worker calls the Replicated API, which validates the license, checks the customer's channel, and returns the allowed `version_label` values. Only version numbers are returned to the customer.
+1. **Download pointer**: Worker calls the Replicated API to create a short-lived server-side session backed by a JWT. The response includes an `X-Terraform-Get` header with the archive URL containing the JWT as a query parameter. The JWT is an opaque, short-lived token. The GitHub credential is stored server-side and never exposed to the customer.


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.Acronyms] Spell out 'JWT' on first use, if it's unfamiliar to the audience.

github-actions · 2026-05-14T21:25:24Z

+
+1. **Discovery**: Worker returns a static registry manifest pointing to the modules API. No auth required.
+1. **List versions**: Worker calls the Replicated API, which validates the license, checks the customer's channel, and returns the allowed `version_label` values. Only version numbers are returned to the customer.
+1. **Download pointer**: Worker calls the Replicated API to create a short-lived server-side session backed by a JWT. The response includes an `X-Terraform-Get` header with the archive URL containing the JWT as a query parameter. The JWT is an opaque, short-lived token. The GitHub credential is stored server-side and never exposed to the customer.


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.Passive] In general, use active voice instead of passive voice ('is stored').

github-actions · 2026-05-14T21:25:24Z

+1. **Discovery**: Worker returns a static registry manifest pointing to the modules API. No auth required.
+1. **List versions**: Worker calls the Replicated API, which validates the license, checks the customer's channel, and returns the allowed `version_label` values. Only version numbers are returned to the customer.
+1. **Download pointer**: Worker calls the Replicated API to create a short-lived server-side session backed by a JWT. The response includes an `X-Terraform-Get` header with the archive URL containing the JWT as a query parameter. The JWT is an opaque, short-lived token. The GitHub credential is stored server-side and never exposed to the customer.
+1. **Tarball download**: Worker validates the JWT, retrieves the GitHub installation credentials from the server-side session, regenerates a fresh GitHub token, fetches the tarball from GitHub, and streams it back. GitHub redirects to a temporary `codeload.github.com` URL; the worker follows this redirect internally so the customer never sees it.


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.Acronyms] Spell out 'JWT' on first use, if it's unfamiliar to the audience.

github-actions · 2026-05-14T21:25:24Z

+
+### Version gating
+
+Versions are gated by the existing release/channel system:


📝 [vale] _{reported by reviewdog 🐶}
[Replicated.Passive] In general, use active voice instead of passive voice ('are gated').

replicated-ci added type::docs Improvements or additions to documentation type::feature labels May 14, 2026

github-actions Bot reviewed May 14, 2026

View reviewed changes

AmberAlston marked this pull request as ready for review May 14, 2026 21:30

AmberAlston requested a review from a team as a code owner May 14, 2026 21:30

		@@ -1,6 +1,10 @@
		# View a customer's Enterprise Portal
		# View a Customer's Enterprise Portal (Classic)

		@@ -1,6 +1,10 @@
		# About the Enterprise Portal
		# About the Enterprise Portal (Classic)

		@@ -1,6 +1,10 @@
		# Enable self-service sign-ups
		# Enable Self-Service Sign-Ups (Classic)


		### Vendor Portal View vs. Customer Portal Version

		The New Portal / Classic Portal toggle at the top of the Enterprise Portal page in Vendor Portal controls which view you see as a vendor. It does not change which portal your customers see. Customer portal versions are controlled individually via the Portal Version toggle on each customer's EP access tab.

		@@ -1,6 +1,10 @@
		# Manage Enterprise Portal customer access
		# Manage Enterprise Portal Customer Access (Classic)


		For information about how end users can sign up for an account and log in to the Enterprise Portal, see [Log in to and Use the Enterprise Portal (New)](/vendor/enterprise-portal-v2-use).

		## Login as Customer


		The login routes to the correct portal version automatically. If the customer is on the new Enterprise Portal, the link opens `{appSlug}.enterpriseportal.app` (or your custom domain). If the customer is on Classic, the link opens `get.replicated.com`.

		## Local CLI Preview


		The CLI pulls a preview container (first run only), starts a local server, and opens the full Enterprise Portal experience at `http://localhost:3000` (auto-increments if the port is busy).

		If you are authenticated with the CLI (`replicated login`, `REPLICATED_API_TOKEN`, or `--token`), a customer switcher dropdown appears in the preview toolbar. Switching customers re-renders the page with that customer's entitlements, channel, and license data applied. Without a token, the preview runs with mock customer data.

		@@ -1,6 +1,10 @@
		# Customize the Enterprise Portal
		# Customize the Enterprise Portal (Classic)


		## Enabling Enterprise Portal for customers

		For vendors using both Classic and New Enterprise Portal (mixed mode), customer access is controlled per-customer:


		## Controlling which customers see Terraform content

		There is no built-in Terraform-specific license field. Customer visibility is controlled through your content repo's `visible_when` entitlements in `toc.yaml`. To gate Terraform content per customer:


		Customers without the entitlement won't see the navigation items or be able to access the module reference docs. You can combine multiple entitlements for more granular control (e.g., per-cloud-provider gating).

		For the proxy registry (module downloads via `terraform init`), access is gated by the customer's license being active and on a channel with promoted releases containing matching version labels. There is no additional per-customer toggle needed for download access. If a customer has a valid license, they can pull any module version available on their channel.


		### Conditionals

		`\{\{#if\}\}`: Show content when a value is truthy. Supports nesting.


		Entitlements are accessible as `\{\{ entitlements.<name> \}\}` for interpolation and `\{\{#if entitlements.<name>\}\}` for conditionals. There are two kinds:

		- Built-in flags: Set on the license via Vendor Portal: `isHelmInstallEnabled`, `isAirgapSupported`, `isEmbeddedClusterDownloadEnabled`, `isEmbeddedClusterMultiNodeEnabled`, `isKotsInstallEnabled`, `isHelmAirgapEnabled`


		## Visibility {#visibility}

		Use `visible_when` to control which customers see which content. All conditions must be satisfied (AND logic).


		### Version gating

		Versions are gated by the existing release/channel system:

Conversation

AmberAlston commented May 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Notes

Vale linter changes

Test plan

Uh oh!

netlify Bot commented May 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for replicated-docs ready!

Uh oh!

netlify Bot commented May 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for replicated-docs-upgrade ready!

Uh oh!

github-actions Bot left a comment

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot left a comment

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 14, 2026

AmberAlston commented May 14, 2026 •

edited

Loading

netlify Bot commented May 14, 2026 •

edited

Loading

netlify Bot commented May 14, 2026 •

edited

Loading