Repository navigation
docs: fill Accounts and admin section landings - #4
Merged
akristen merged 10 commits intoSep 2, 2026
Merged
Conversation
…ndings These section indexes used render: never, so the published URLs had no page. They now render as chooser landings with grids of child topics. Co-authored-by: Cursor <cursoragent@cursor.com>
The Subscription and billing parent was carrying the portal tutorial. That content now lives on Manage billing, the parent is a plans chooser, and #credits/#usage links point at the new page. Agentic Platform stays off the parent table and grids. Co-authored-by: Cursor <cursoragent@cursor.com>
Account-type comparison belongs on the Accounts landing. Organization and Manage grids were missing Activity logs, Insights, Teams, Seats, and Licenses even though those pages already exist. Co-authored-by: Cursor <cursoragent@cursor.com>
Plans was repeating Manage plans instead of helping readers choose. FAQs needed a short map of each collection. The Manuals Accounts and admin grid was missing Support and Release notes from the sidebar group. Co-authored-by: Cursor <cursoragent@cursor.com>
Account types, OIDC versus OAT, and core versus custom roles each had a second copy after the parent landings took that job. Company keeps owner and seat rules and links up to the hierarchy diagram. Co-authored-by: Cursor <cursoragent@cursor.com>
The page was still titled Security for developers and omitted SSO, provisioning, roles, OATs, and OIDC even though those pages already live in this section. Co-authored-by: Cursor <cursoragent@cursor.com>
The page was still framed for developers and split into three grids. Individual and organization sections plus one child grid match the rest of Accounts and admin. Co-authored-by: Cursor <cursoragent@cursor.com>
…ages The banner only appeared on enterprise admin docs, and the landing linked choosers instead of 2FA, PAT, SSO, OIDC, and OATs. Co-authored-by: Cursor <cursoragent@cursor.com>
SSO and provisioning come before automation credentials, and roles apply after members join. Co-authored-by: Cursor <cursoragent@cursor.com>
Company lived under Organization, so the Accounts landing could not treat it as a sibling account type. A top-level section matches how owners switch between org and company. Co-authored-by: Cursor <cursoragent@cursor.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
Fills empty and thin Accounts and admin index pages so Authentication, Access tokens, Manage billing, Accounts, Plans, FAQs, and Security are real landings instead of stubs or leftover developer grids. Promotes Company to a sibling of Organization, and adds Personal/Pro summary bars on individual security pages.
Related to docker#25982
@netlify /security/
Generated by Cursor