docs: how to change the company name shown on invoices

[djgrove]

Customers regularly file support tickets asking how to change the company name shown on their Pulumi invoices. The name is sourced from their organization's display name (Settings > General > Display Name), and the sync to Stripe is automatic — but this is not documented anywhere, so users don't realize they can self-serve. Ops handles each ticket manually.

This adds a short "Changing the company name on invoices" section to the existing Pulumi Cloud Organizations page, placed directly after "Updating billing information" so it sits with related billing self-service content.

[github-actions]

Pre-merge Review — Last updated 2026-06-26T00:00:00Z

Tip

Summary: This PR adds a "Changing the company name on invoices" section to the organizations admin page (content/docs/administration/organizations-teams/organizations.md), explaining that the invoice company name comes from the organization's display name and how to change it. A fix push (ec76f38) corrected the permission scope (organization:billing → organization:rename, Admin-only per RBAC scopes) and replaced the unverifiable "planned enhancement" roadmap claim with a plain contact-support link. No outstanding findings remain.

Review confidence:

Dimension	Level	Notes
mechanics	HIGH
facts	HIGH
cross-sibling consistency	HIGH	Read all 4 directory peers plus the authoritative RBAC scopes doc.

Investigation log

• Cross-sibling reads: 4 of 4 siblings (plus the RBAC scopes source of truth, rbac/scopes/org-settings.md)
• External claim verification: 4 of 5 claims verified (1 unverifiable, 0 contradicted) · 4 specialists (numerical, cross-reference, capability, framing); 0 cross-specialist corroborations · routed: 0 inline, 4 Pass 1, 0 Pass 2, 1 Pass 3 (verified 0, contradicted 0, unverifiable 1).
• Cited-claim spot-checks: not run (no cited claims)
• Frontmatter sweep: ran on body + meta_desc
• Temporal-trigger sweep: not run (no trigger words)
• Code execution: not run (no static/programs/ change)
• Code-examples checks: not run (no fenced code blocks in content files)
• Editorial-balance pass: not run (not under content/blog/)

🚨 Outstanding	⚠️ Low-confidence	💡 Pre-existing	✅ Resolved
0	0	0	2

🔍 Verification trail

6 claims extracted · 4 verified · 1 unverifiable · 1 mismatch

• L107 in content/docs/administration/organizations-teams/organizations.md "Updating an organization's display name in Pulumi will be reflected on the next invoice after the change." → ✅ verified (evidence: The file at L107 (within the "Changing the company name on invoices" section) states: "To change it, update the display name and the change will be reflected on your next invoice." This directly confirms the claim.; source: repo:content/docs/administration/organizations-teams/organizations.md)
• L107 in content/docs/administration/organizations-teams/organizations.md "Display name updates take effect within a short time after saving." → ✅ verified (evidence: The file at the relevant section states: "Updates take effect within a short time after saving." — directly matching the claim about display name updates taking effect within a short time after saving.; source: repo:content/docs/administration/organizations-teams/organizations.md)
• L111-112 in content/docs/administration/organizations-teams/organizations.md "To update an organization's display name in Pulumi, a user navigates to Settings > General and updates the Display Name field." → ✅ verified (evidence: The documentation at the relevant section states: "To update your organization's display name: 1. Navigate to Settings > General. 1. Update the Display Name field and save your changes." This exactly matches the claim.; source: repo:content/docs/administration/organizations-teams/organizations.md)
• L114 in content/docs/administration/organizations-teams/organizations.md "Updating the organization's display name requires the organization:billing permission." → ✅ verified (evidence: The file at content/docs/administration/organizations-teams/organizations.md explicitly stated: "Updating the display name requires the organization:billing permission, which is granted to organization admins and Billing Managers." (initial review; text corrected in ec76f38); source: repo:content/docs/administration/organizations-teams/organizations.md)
• L116 in content/docs/administration/organizations-teams/organizations.md "Distinct legal billing names on invoices (different from the organization's product-facing display name) are a planned enhancement in Pulumi." → 🤷 unverifiable (evidence: No public Pulumi documentation, support page, or search result mentions a planned enhancement for distinct legal billing names on invoices separate from an organization's display name. The source hint (/support/) did not surface any corrob…; source: WebSearch ran query "Pulumi organization billing name invoice display name planned feature support"; top results didn't address the claim.; intuition: Roadmap/planned-feature claims are inherently volatile and often sourced from internal support tickets or private commu…)
• L114 in content/docs/administration/organizations-teams/organizations.md "Changing the display name requires organization:billing, granted to organization admins and Billing Managers" → ⚔️ mismatch (evidence: The RBAC scopes source of truth gates renaming the organization behind a different scope — organization:rename ("Change the name of the organization. This updates the organization's display name across the platform"), granted to Admin only, not Billing Manager. organization:billing covers "billing settings and payment methods… invoices and payment history," not renaming. By the authoritative grants, a Billing Manager cannot change the display name.; source: repo:content/docs/administration/access-identity/rbac/scopes/org-settings.md)

🚨 Outstanding in this PR

No outstanding findings.

⚠️ Low-confidence

No low-confidence findings.

💡 Pre-existing issues in touched files (optional)

No pre-existing issues in touched files.

✅ Resolved since last review

• [L114] content/docs/administration/organizations-teams/organizations.md — Permission scope corrected from organization:billing to organization:rename, and role grants narrowed to organization admins only (removing Billing Managers). Now matches the RBAC source of truth. (resolved in ec76f38)

• [L116] content/docs/administration/organizations-teams/organizations.md — "Planned enhancement" roadmap claim removed; replaced with a plain contact-support link, eliminating the unverifiable forward-looking statement. (resolved in ec76f38)

📜 Review history

• 2026-06-25T23:54:37Z — Cross-sibling check: doc gates the display-name change on organization:billing (Billing Managers), but RBAC reserves org renaming for the Admin-only organization:rename scope (🚨); one unverifiable roadmap claim (⚠️). (61656fb)
• 2026-06-26T00:00:00Z — history rewritten since last review; re-reviewed against HEAD (ec76f38); both findings resolved: permission scope corrected, roadmap claim removed.

---

Need a re-review? Want to dispute a finding? Mention @claude and include #update-review.
(For ad-hoc questions or fixes, just @claude — no hashtag.)

[pulumi-bot]

Your site preview for commit ec76f38 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-19893-ec76f38f.s3-website.us-west-2.amazonaws.com

[djgrove]

Both findings landed.

🚨 Outstanding (L114, permission gating): Confirmed against rbac/scopes/org-settings.md:134 — organization:rename is Admin-only; organization:billing (L130) explicitly covers billing settings, payment methods, invoices, and payment history but not renaming. Page now matches the source of truth. Fixed in 50fc07c.

⚠️ Low-confidence (L116, "planned enhancement"): Agreed, dropped the roadmap framing. The "contact support" routing stays as-is, since support has a known manual workaround. Fixed in a1d7e36.

[Copilot]

Pull request overview

Adds self-serve guidance to the Pulumi Cloud Organizations documentation so customers can update the company name shown on invoices by changing their organization display name, reducing support ticket volume.

Changes:

• Adds a new “Changing the company name on invoices” section immediately after “Updating billing information”.
• Documents the UI path to update an organization display name and the required organization:rename permission.
• Adds a support escalation note for cases where the legal entity name must differ from the product-facing display name.

[djgrove]

@claude #update-review

[github-actions]

🤖 Review updated on @djgrove's request.

[CamSoper]

Automated rubber stamp approval applied

---

Generated by Claude Code