[DOCS-XXXXX] Document the team filter and its use as a template variable

[tomnof]

What does this PR do? What is the motivation?

Fixes DOCS-XXXXX

Updates the team filter documentation and documents the team filter as a dashboard and notebook template variable.

Team filter (account_management/teams/)

• Rewrites the team filter section to describe the current control: one list covering both Datadog Teams and team tag values, with all teams in the organization available.
• Removes documentation for functionality that no longer exists: favoriting a team to expand filter scope, the My Teams label, and the on/off toggle.
• Adds pin behavior, including that pinned selections are stored per browser and per device, and deep-link behavior.
• Adds shift+click selection modes for choosing a team without its subteams, or its subteams without the team.
• Adds search behavior: case-insensitive substring matching against handle and display name, with double quotes for exact matches.
• Replaces the stale screenshot with the current one. A fresh capture is still needed (see below).

Template variables (dashboards/template_variables.md)

• Documents that a template variable on the team tag key renders as the team filter, and that hierarchy-aware selection appears only for that tag key. This is the answer to the recurring question of why one dashboard's team filter shows hierarchy and another's does not.
• Adds a guide for using the team filter against a different tag key (team_attribution, attributes.team, usr.team) by defining the variable on team and referencing $team.value in widget queries, with before-and-after examples and how multi-select and hierarchy selections resolve.

Also updated: dashboard list, notebooks, and IDP catalog ownership pages that referenced the removed My Teams toggle or label.

Merge readiness

• Ready for merge

For Datadog employees:

• ⚠️ Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR.
• 🤖 New: Comment with /review to run an automated check that catches common issues before a Documentation team member reviews your PR.

AI assistance

Drafted with Claude Code. Behavior of $team.value under multi-select and hierarchy selection was verified against a live dashboard by inspecting resolved widget queries.

Additional notes

Screenshot still needed: static/images/account_management/teams/team-filter.png shows the old two-control layout with the My Teams label, per-team toggles, and Add Favorites. It is no longer referenced, but a new capture showing the unified control with the pin and a team tags section would improve the page.

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/tom.nof/team-filter-template-variable-docs/account_management/teams/
• https://docs-staging.datadoghq.com/tom.nof/team-filter-template-variable-docs/dashboards/list/
• https://docs-staging.datadoghq.com/tom.nof/team-filter-template-variable-docs/dashboards/template_variables
• https://docs-staging.datadoghq.com/tom.nof/team-filter-template-variable-docs/infrastructure/list
• https://docs-staging.datadoghq.com/tom.nof/team-filter-template-variable-docs/internal_developer_portal/catalog/set_up/ownership
• https://docs-staging.datadoghq.com/tom.nof/team-filter-template-variable-docs/notebooks/
• https://docs-staging.datadoghq.com/tom.nof/team-filter-template-variable-docs/real_user_monitoring/ownership_of_views

[drichards-87]

Created DOCS-15380 for Docs Team review.

[OliviaShoup]

thank you for the PR! this looks really good. i left some inline suggestions

three things besides the comments

1. deleting teams_filter_hierarchies.png breaks a French page

hugo/static/images/account_management/teams/teams_filter_hierarchies.png is still referenced at hugo/content/fr/account_management/teams/manage.md:68. the English page uses teams_filter_hierarchies2.png, so these are two separate files and the English side is unaffected, but removing this one leaves a broken image on the FR site. simplest fix is to leave the file in place; otherwise the FR change needs to go through localization rather than a hand-edit

2. screenshots

did you want me to take care of that, or were you planning on it? either way is fine with me!

**3. Team tags vs All Teams **

does the ALL TEAMS section contain Datadog Teams you are not a member of,
team tag values with no matching Team, or both?

asking because teams/_index.md:108 describes it as "team tag values found on
your data that have no matching Datadog Team," and a few things in the
screenshots point the other way:

• the section is labeled ALL TEAMS in all three captures, and the page's own
  alt text on line 110 calls it "an All Teams section." the body and the alt text
  disagree with each other
• Singapore SE in that section is annotated "1 Subteam." subteams belong to
  Datadog Teams, so that row looks like a real Team rather than a tag value
• the rows read like Team display names ([Demo] Caroline H.'s Team, emoji
  prefixes) rather than the lowercase-hyphenated handles that the IDP ownership
  page in this PR recommends

worth settling before merge because the same claim appears in three files:
teams/_index.md:108, template_variables.md:76, and notebooks/_index.md:193.
it also affects the "Each section of the filter lists up to 50 items" line, since
that depends on what counts as a section

if the section holds both Teams and orphan tag values, the fix may just be using
the UI's label and broadening the description.

please let me know if you want to talk about any of this!

[OliviaShoup]

the All Teams list in team-template-variable.png runs [Caroline], [Demo], [grega], [sblin], Singapore SE, JP-SDR which isn't alphabetical by display name. does it sort by handle? worth saying which, since the search section just below notes that both handle and display name are searched

[tomnof]

Checked this. It sorts alphabetically by display name, case-insensitive, with emoji prefixes ignored for sorting — so [Caroline], [Demo], [grega], [sblin] are ordered on the bracketed prefix, and Singapore SE / JP-SDR fall into a leading group I couldn't account for. Since I can't explain that leading group, I'd rather not commit the docs to a precise rule, so I've left the line general. Happy to tighten it if you'd prefer.

[OliviaShoup]

"behaves like the time range pin" assumes the reader already knows that control. a short definition or a link would be helpful, like "...and carries the selection to other pages the same way the time range pin does."

[OliviaShoup]

/review

[github-actions]

🤖 Automated review by Claude. AI-generated; verify before acting.

Content is well-structured and clearly explains the new team filter behavior. A couple of small style/consistency observations below — no blockers.

_{Reviewed 01e96e771a3b22b1ee5adfc629077e7eded520db — workflow run}

[tomnof]

Thanks for the review — all three settled:

1. FR image. Good catch. Restored teams_filter_hierarchies.png; the FR page is untouched so any change there can go through localization.

2. Screenshots. I took care of them — captured in the Datadog Demo org.

3. ALL TEAMS. You were right, and my original description was wrong. That section holds Datadog Teams in the org, including ones you're not a member of — not orphan tag values. The subteam counts and display names you spotted were the giveaway. The filter now documents three sections: your teams, All Teams, and team tags (the orphan team tag values, which do get their own section). Body and alt text agree now, and I corrected the same claim in template_variables.md and notebooks/_index.md. The 50-item line still holds — it's per section.

One heads-up on the suggestion-accept flow: your condensed-instructions suggestion ended up applied three times over when it was accepted through GitHub's "Commit suggestion" button. The button only applies the suggestion block, so it couldn't honor your "the two paragraphs above would need deleting alongside it" caveat, and the earlier copies stayed. My merge resolved it and the section reads correctly now — flagging it in case you hit the same thing on other PRs.