Refresh Administration section of the site

[jkodroff]

Quick notes for future refinement:

• https://www.pulumi.com/docs/administration/organizations-teams/organizations/ is way too long
• Consider phasing out the entire "organizations and teams" nav and merging with IAM or moving to a more standard IA: Concepts, etc. Leaning in this direction, since the OIDC stuff (e.g. https://www.pulumi.com/docs/administration/access-identity/oidc-issuers/kubernetes-eks/) are clearly guides.
• https://www.pulumi.com/docs/administration/organizations-teams/accounts/ also needs screenshots removed
• Why does this get its own page specifically for ESC? Why not a specific reference page or a general audit logs guide? https://www.pulumi.com/docs/esc/administration/audit-logs/ (It's also double-listed in the nav)

[workprentice]

Since I had capacity left in this cycle, here's a scoped strawman for the four notes above, offered as a starting point for you or another docs lead to accept, modify, or reject; I'm not proposing to implement any of this without sign-off, and I have not opened a PR against it.

Current shape (confirmed by reading the content tree)

• administration/organizations-teams/ holds five pages: organizations, teams, accounts, agent-accounts, billing-managers.
• administration/access-identity/ already holds rbac, saml, scim, and oidc-issuers/ (a guide-shaped subsection with per-provider pages).
• Audit logs exist as two separate pages: administration/security-compliance/audit-logs/ (general) and esc/administration/audit-logs.md (ESC-specific). The ESC page is nav-listed twice, under both pulumi-esc-admin and administration-security-compliance, which is the double-listing you flagged.

Strawman

1. Merge organizations-teams into a concepts or access-identity grouping rather than deleting it. organizations.md and teams.md are conceptual/reference material (what an org and a team are, how membership works) that IAM pages currently assume as background; accounts.md, agent-accounts.md, and billing-managers.md are closer to account-management how-tos. Splitting along that seam avoids a single oversized "organizations and teams" page while not asking access-identity to absorb pure concepts.
2. organizations.md is long because it mixes concept, setup steps, and settings reference. Trimming it likely means moving setup steps into the onboarding guide (which already exists at administration/onboarding-guide/) and settings-reference detail into its own reference page, leaving the parent page as a short concept overview with links out.
3. The OIDC pages are already guide-shaped (access-identity/oidc-issuers/kubernetes-eks/ etc.) and read naturally as guides today; agree they don't need to move, just confirming they're not part of what's being restructured.
4. Screenshot removal on accounts.md is a mechanical follow-up, not an IA question. Independent of the rest, low-risk, and something I'd fold into a routine freshness pass rather than treat as part of the restructuring PR.
5. On the ESC audit-logs double-listing: the two pages cover different scopes (product-wide audit logs vs. ESC-specific audit-logs) rather than being true duplicates, but the ESC page appearing under both esc-home and administration-security-compliance menus is a nav configuration issue independent of content. Two options: keep both pages but list the ESC one only under esc-home and cross-link from the general audit-logs page, or fold the ESC-specific content into the general page as an ESC subsection. I'd lean toward the first since ESC audit logs have product-specific fields (environment/secrets access events) that don't belong diluting the general page, but that's a judgment call for whoever owns the ESC docs.

Happy to implement whichever direction you land on once there's a decision; this is meant to save you the trawl through the content tree, not to preempt the call.

[jkodroff]

This got refined into better issues. No longer needed. Closing.