Add Multi-Tenant Usage Metering and Billing partner docs (PSAOKR-5462) - #38581
Draft
lucarelli111 wants to merge 26 commits into
Draft
Add Multi-Tenant Usage Metering and Billing partner docs (PSAOKR-5462)#38581lucarelli111 wants to merge 26 commits into
lucarelli111 wants to merge 26 commits into
Conversation
New section under content/en/partners/multi_tenant_billing/ covering the Admin Org: what it is and its capabilities (including preview features), requesting one, Trial Org provisioning, cost/usage visibility, and troubleshooting.
Merge Overview/capability-list redundancy into concise, action-oriented
sections modeled on cloud_cost_management/_index.md and
plan_and_usage/_index.md. Replace ad-hoc HTML alert divs with the
site's bold-prefixed Note/Important convention, use {{< ui >}}
consistently for in-app element names, and tighten prose.
…view / Getting started / Use cases / Troubleshooting)
Contributor
…de's overuse guidance
…ecklist
- Fix Vale violation: 'ensures' -> rephrase
- Wrap remaining bold-only UI element names in {{< ui >}} for consistency
(Trial Org Provisioning dashboard, Customer Pricing, Customer Contracts tabs)
- Match heading/link-text capitalization to actual page titles (Cost and
Usage Visibility, Trial Org Provisioning) per the title-consistency check
- Remove orphaned further_reading front matter on cost-and-usage-visibility.md
(never rendered - no whats-next partial call on that page - and duplicated
its own inline reference links)
Placeholder 1x1 PNGs at static/images/partners/multi_tenant_billing/ for
each {{< img >}} reference in _index.md - replace with real screenshots
before merging.
- New content/en/partners/multi_tenant_billing/centralized-usage-metrics.md, based on the internal EUM/UM/Admin Org roll-up doc, filtered to what's partner-facing (drops internal Mosaic/consul-config flags, Slack channel, and C&A team ownership note - replaced with the standard partner-support@datadoghq.com contact for enabling UM roll-up) - No longer marked (Preview) - capability is GA - _index.md: shortened teaser section, added nav/whatsnext links to the new page, updated Use Cases table - cost-and-usage-visibility.md: removed now-duplicated Centralized Usage Metrics section, cross-links to the new page instead - Added the new page to config/_default/menus/partners.en.yaml
Datadog's own billing nav links to the 'Estimated Usage Metrics' page with the text 'Usage Metrics', treating 'estimated' as a plain descriptive word rather than a branded acronym pair. EUM/UM are internal-only shorthand.
…nshots - List the 6 real Usage Metering API endpoints with links and the correct include_connected_accounts / filter[include_connected_accounts] flag per endpoint, on both _index.md and cost-and-usage-visibility.md - Correct Trial Org Provisioning: it's the Admin Org homepage, not a Dashboards-menu item (troubleshooting.md, trial-org-provisioning.md, _index.md) - Remove plan_and_usage_admin_org.png screenshot/reference - redundant with the linked Plan and Usage Experience for Partners page - Add real screenshots: admin_org_hierarchy, customer_contracts, customer_pricing, usage_metrics_rollup
- New customer-onboarding.md, based on the internal Customer Onboarding Process for Partner doc: register deal -> create Trial Org -> share Trial Org ID with the PSM. Corrects the source's outdated 'navigate to Dashboards' instruction and drops dated 'as of <date>' framing. - Wired into _index.md (Overview pointer, first whatsnext link) and the left nav (weight 5, ahead of Requesting an Admin Org). - Removed the three _index.md H3 sections that duplicated their own dedicated pages (Cost and Usage Visibility, Trial Org Provisioning, Centralized Usage Metrics) - those topics now live only in the Use Cases table + their dedicated page, matching how tracing/_index.md only keeps full sections for topics without a separate deep page. - Moved the Trial Org Provisioning and Centralized Usage Metrics screenshots onto their dedicated pages along with the removed sections. - trial-org-provisioning.md: removed the inaccurate 'PSM is notified automatically' claim, fixed a leftover step-numbering gap. - centralized-usage-metrics.md: dropped the tag descriptions to match the source's literal parent/child framing; removed the preview/enable section now that the capability is GA.
- Trial Org usage is not visible from the Admin Org until the customer org has an active contract tied to the partnership (confirmed) - fixed trial-org-provisioning.md and customer-onboarding.md, which both implied automatic rollup on Trial Org creation. - _index.md: fixed 'manage billing' contradicting the read-only-access alert two lines below - changed to 'view billing'. - Updated admin_org_hierarchy.png screenshot.
…tor in request - _index.md: clarify the read-only/no-billing-changes alert applies by default, and the Preview capabilities below add supported pricing and contract-management workflows (was a flat contradiction otherwise). - requesting-an-admin-org.md: note that partners planning to provision trials should include the Trial Org Creator capability in the initial request, since it's a separate opt-in capability, not bundled by default.
…ricing, not Datadog's own estimate
- whatsnext/nav order: Requesting an Admin Org -> Onboarding a New
Customer -> Trial Org Provisioning -> Cost and Usage Visibility ->
Centralized Usage Metrics -> Troubleshooting (get the org before
using it).
- Use Cases table: rename 'How an Admin Org helps' column to
'Capability', and name the capability directly ('[X]: does Y')
instead of 'Use X to Y' in every row - matches the Name: description
pattern already used in the whatsnext block.
- The page only had two real facts (prerequisites, contact) surrounded by internal-mechanics detail irrelevant to a partner (Partner Plan, separate contract, US1-site creation, read-only access already stated in the Getting started alert). Deleted it and folded the prerequisites + contact directly into _index.md's Getting started section. - Contact is now partner-support@datadoghq.com only, not 'or a PSM' - the PSM alternative wasn't the intended request path. - Updated all cross-references (customer-onboarding.md, cost-and-usage-visibility.md, centralized-usage-metrics.md) and the left nav to drop the removed page. - cost-and-usage-visibility.md: softened 'The same data is available programmatically' to 'Cost and usage data is also available...' - the API and UI aren't guaranteed to return identical data.
…iew gaps - Broaden 'resell or MSP partner' to include systems integrator partners throughout (Overview + eligibility bullet). - Replace 'PSM'/'Partner Sales Manager' with 'partner account team', matching how other Datadog partner docs refer to this contact (partner-support@datadoghq.com / 'Datadog partner representative' are the established terms; naming a specific role isn't). - customer-onboarding.md: merge the trial-to-paid transition into the existing 'Share the Trial Org' section instead of a new redundant section - continue working with the partner account team through to a signed contract. - trial-org-provisioning.md: add a 'Find the Trial Org ID' fallback section (browser console / bookmarklet), adapted from the equivalent section in getting_started/laying-the-groundwork.md, for partners who didn't capture the org ID from the result panel. - cost-and-usage-visibility.md: state that a Trial Org's usage isn't included until its customer org is connected (previously only stated on other pages, not the page most likely to be checked for it), and that final invoices are the authoritative source for billed amounts, not the estimated/projected views shown here.
…reenshot placement
- Registration/eligibility now uses the official DPN terminology
(Solution Provider) instead of the earlier guessed resell/MSP/SI
enumeration.
- Add a Register Now link (partners.datadoghq.com/s/login/) for
partners not yet registered, before the partner-support contact
instruction for already-registered partners.
- Move the Partner Portal registration screenshot to sit right after
the Register Now sentence instead of before it.
- Trial Org Creator note reformatted as a proper Note callout.
Full review pass against our style rules across all six pages:
- Fixed redundant phrasing ('by Datadog' after 'Datadog partner',
'as early as possible, even at an early stage').
- Genericized the remaining 'Partner Solutions Architect (PSA)'
reference to 'partner account team', matching the PSM fix.
- Updated stale scope language now that Onboarding a New Customer
covers the full path through contract signature, not just Trial Org
creation - 'a live Trial Org' -> 'a connected customer organization'
in _index.md (twice) and customer-onboarding.md's description/Overview,
and the Overview's 'two steps' updated to the actual three-part flow.
- Verified no Vale-flagged words, filler words, you/your, orphaned
refs, or dangling links to the removed Requesting an Admin Org page
across all six files.
…w, fold Trial Org Creator line into prose The two notes sat side-by-side in Getting started with mismatched styles (one HTML alert box, one plain bold text). Moved the read-only access alert to the Overview where it fits conceptually (describing what an Admin Org is/does), and folded the short Trial Org Creator sentence into the preceding paragraph instead of styling it as its own note.
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
content/en/partners/multi_tenant_billing/covering the Admin Org: what it is and its capabilities (including Preview features), requesting one, Trial Org provisioning, cost/usage visibility, and troubleshooting.AI assistance
Content sourced from internal Confluence pages and partner enablement decks, and structured/worded to match existing doc patterns in this repo (
tracing/_index.md,account_management/plan_and_usage/partner_experience.md).Test plan
{{< img >}}tags (marked with TODO comments)