Document cost and budget visibility for non-billing users#7273
Draft
sakurai-youhei wants to merge 2 commits into
Draft
Document cost and budget visibility for non-billing users#7273sakurai-youhei wants to merge 2 commits into
sakurai-youhei wants to merge 2 commits into
Conversation
Organization members with resource-scoped roles (Admin, Editor, Viewer) can now view usage, costs, and budgets for the hosted deployments, serverless projects, and connected clusters they have access to, without needing Billing admin or Organization owner rights. This updates the three affected pages to describe who can see and manage billing data under the new access model, while keeping organization-wide financial data (credit balance, billing history, invoices, and organization-scoped budgets) owner/admin-only as before. Refs elastic/platform-billing#7643 (internal tracking issue). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
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. |
Contributor
Contributor
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! 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. |
Members with a connected cluster access role also gain usage/cost and budget visibility for the connected clusters in their scope, under the same Expanded Non-Billing User Access model already documented for cloud resource access roles. This adds the parallel note that was missing from the Connected cluster access roles section. Refs elastic/platform-billing#7643 (internal tracking issue). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the Expanded Non-Billing User Access change: organization members with a cloud resource access role (Admin, Editor, Viewer) can now view usage, costs, and manage budgets for the hosted deployments, serverless projects, and connected clusters they already have access to — without needing Billing admin or Organization owner rights. Organization-wide financial data (credit balance, billing history, invoices, and organization-scoped budgets) remains owner/admin-only, unchanged.
deploy-manage/users-roles/cloud-organization/user-roles.md: notes that both cloud resource access roles and connected cluster access roles also grant usage/cost/budget visibility for resources in their scope, linking to the two billing pages below.deploy-manage/cloud-organization/billing/monitor-analyze-usage.md: adds a who-can-view breakdown (organization-wide for owners/billing admins vs. resource-scoped for other roles), clarifies that users see the full available cost history for resources they currently have access to, and adds a note that organization-wide financial data stays owner/admin-only.deploy-manage/cloud-organization/billing/manage-billing-notifications.md: clarifies who can create, view, and manage a budget depending on its scope (organization vs. cloud resource).Internal tracking issue: elastic/platform-billing#7643
Generative AI disclosure
Tool(s) and model(s) used: Claude Code (Claude Opus 4.8)