Document unified addSettingsLink and related deprecations in admin nav docs

[unrevised6419]

Description

Updates docs/cms/plugins-development/admin-navigation-settings.md to match the current StrapiApp / Router source in strapi/strapi.

Unified addSettingsLink API

• Promote addSettingsLink(sectionId | section, link | links) as the single recommended method. It now accepts either a section id string (extend existing section) or a section object { id, intlLabel } (create a new section), and either a single link or an array of links as the second argument.
• Update Tldr, "Creating a new settings section" example, and "Adding links to existing settings sections" example accordingly.

Document deprecated methods

• Add a dedicated ## Deprecated methods section with ❌/✅ migration snippets for:
  • createSettingSection(section, links) — replace with addSettingsLink(section, links).
  • addSettingsLinks(sectionId, links) — replace with singular addSettingsLink(sectionId, links).
• Add inline :::caution admonitions next to each primary example pointing at the deprecated counterpart.
• Clarify that addSettingsLinks is still exposed on the plugin bootstrap argument bag, while createSettingSection is only reachable from register(app).

Fix parameter-table drift (required column + types)
Reconciled against packages/core/admin/admin/src/core/apis/router.tsx (MenuItem, UnloadedSettingsLink):

• permissions is required by the type contract (pass [] for no restrictions) — was previously marked optional.
• Component is optional (omitting registers no route, label-only entry) — was previously marked required.
• icon type corrected from React.Component to React.ElementType.
• Added missing optional params: target, notificationsCount, exact (menu link); position, exact (settings link).

Misc

• Updated the "Path conventions for to" table to label rows by the unified API (with section object / with section id) rather than the deprecated createSettingSection.

Related issue(s)/PR(s)

Source of truth for the API surface documented here: strapi/strapi#26433.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
documentation	Ready	Preview, Comment	Jun 1, 2026 2:05pm

[pwizla]

Thank you very much, @unrevised6419!
LGTM from a docs POV. I edited some content for formatting compliance, incl. the PR title.
Now waiting for the corresponding strapi/strapi PR to be merged, so I'm applying the flag: merge pending releaselabel.

[unrevised6419]

To be noted, that PR only fixes the TypeScript definition, the runtime actually behaves exactly how is in this PR

[unrevised6419]

@pwizla the linked PR was merged and released in https://github.com/strapi/strapi/releases/tag/v5.49.0. This can be merged

[pwizla]

Thank you for the ping, @unrevised6419
The repo was on a soft freeze while I was QAing and deploying the new website version. I've just finished reviewing your PR, and improved it slightly. The PR is now approved, merged, should be live on docs.strapi.io in a few minutes, and will be mentioned in the next weekly snapshot release (7.0.1, probably today or tomorrow). Thanks again for your valuable contribution!