Multi-org GA content#5320
Conversation
Elastic Docs Style Checker (Vale)Summary: 4 suggestions found 💡 Suggestions (4): Optional style improvements. Apply when helpful.
The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
|
done |
|
|
|
missing:
|
# Conflicts: # deploy-manage/cloud-organization/_snippets/switch-orgs.md # deploy-manage/cloud-organization/_snippets/view-orgs.md # deploy-manage/cloud-organization/manage-multiple-organizations.md # deploy-manage/deploy/elastic-cloud/azure-native-isv-service-logs-metrics.md # deploy-manage/deploy/elastic-cloud/azure-native-isv-service-troubleshooting.md # deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md # deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md # deploy-manage/toc.yml # redirects.yml
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
There was a problem hiding this comment.
Docs review summary
Focus areas
- Style and clarity: Newly added content is clear and well-structured. One Vale Wordiness hit ("all of its" → "all its") and one Vale WordChoice hit (
may→might) in new content — both have inline suggestions. - Jargon: No problematic unexplained jargon. Multi-org concepts are well-explained throughout.
- Frontmatter and applies_to: Both new pages (
switch-organizations.md,marketplace-trial-conversion.md) are missingdescription.switch-organizations.mdalso has aproducts/applies_tomismatch (serverless: gaset but onlycloud-hostedlisted). See inline comments. Theapplies_to: ess→echcorrection inmanage-users.mdlooks intentional and correct. - Content type fit: The new how-to and concept pages follow the expected structure for their content types.
marketplace-trial-conversion.mdis a clean how-to;switch-organizations.mdcovers concept + procedure appropriately. - Parent issue satisfaction: The PR satisfies the GA multi-org documentation requirements described in its body across all key user and admin flows. The open question raised by the author — whether a callout is needed for AutoOps behavior inconsistencies — is not addressed in the current content; worth confirming before merge.
Nits
deploy-manage/cloud-organization/manage-multiple-organizations.md: missingdescriptionin frontmatter (pre-existing gap, but this PR is a good opportunity to add one).deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md: also missingdescriptionafter substantial expansion in this PR.deploy-manage/cloud-organization.md: missing trailing newline at end of file (the diff ends with\ No newline at end of file).
Notes
- The
% is this still true?comment inaws-marketplace.md(inline comment filed) is a self-noted accuracy question; flagged so it isn't merged unresolved. - Pre-existing
**Organization** > **Members**menu arrow format inmanage-users.md(line 50, ValeMenuArrowsBold) was not changed in this PR and is out of scope.
Generated by Docs review agent for issue #5320 · 92.3 AIC · ⌖ 16 AIC · ⊞ 10.7K
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
alxchalkias
left a comment
There was a problem hiding this comment.
Initial review. Will do another one later today
Co-authored-by: Alex Chalkias <34575586+alxchalkias@users.noreply.github.com>
Summary
Fixes https://github.com/elastic/docs-content-internal/issues/833
Builds on #5351
Open questions
Changes
Also made some tag cleanup changes, but those don't impact the display
Admin facing
- viewing all of the orgs you have access to
- creating a new org
- inviting users to join additional orgs
- seeing users' org memberships
- reconciling alternative email addresses
Cross-references the user-facing join/leave and view/switch pages so admins know where members go for their tasks.Removed the connection between the email address and the org / 1email:1org restriction, clarified that a user can be a member of multiple orgs. Now talks about trial:org limitations
Updated "Remove trial limitations" to mention marketplace conversion alongside credit card
Marketplace stuff
New "Multi-org accounts and the Azure portal" section documenting that the Azure portal can't handle ambiguous multi-org situations (no org picker)
End user facing
Generative AI disclosure
Tool(s) and model(s) used: cursor auto