Skip to content

docs: update internal user filtering settings navigation path#18785

Open
inkeep[bot] wants to merge 2 commits into
masterfrom
docs-writer-ai-update-2026-07-22T06-50-36-374Z-g12tn7
Open

docs: update internal user filtering settings navigation path#18785
inkeep[bot] wants to merge 2 commits into
masterfrom
docs-writer-ai-update-2026-07-22T06-50-36-374Z-g12tn7

Conversation

@inkeep

@inkeep inkeep Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Changes

Updates documentation to reflect the new location of the "Filter out internal and test users" setting, which was moved from Settings → Product analytics to Settings → Customization in PostHog/posthog#72596.

Files updated

  1. contents/docs/product-analytics/trends/filters.mdx

    • Updated link text from "Product Analytics settings" to "Customization settings"
    • Updated URL path from /settings/project-product-analytics#internal-user-filtering to /settings/project-customization#internal-user-filtering
  2. contents/tutorials/filter-internal-users.mdx

    • Updated link text from "Product Analytics settings" to "Customization settings"
    • Updated URL path from /settings/project-product-analytics#internal-user-filtering to /settings/project-customization#internal-user-filtering

Why this change

The setting applies to all PostHog products (insights, web analytics, revenue analytics, session replay, and CDP destinations), so it was moved to the Customization section with other project-wide preferences. While the old URLs redirect automatically, the documentation should reflect the current UI navigation path.


This PR was created by the Inkeep Content Writer agent, which is maintained by the Docs and Wizard team. Please reach out on Slack for help if needed.

@github-actions

github-actions Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Deploy preview

Status Details Updated (UTC)
🟢 Ready View preview Jul 22, 2026 07:03AM

@github-actions

Copy link
Copy Markdown
Contributor

Vale prose linter → found 0 errors, 15 warnings, 3 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

contents/docs/product-analytics/trends/filters.mdx — 0 errors, 8 warnings, 3 suggestions
Line Severity Message Rule
11:66 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
13:67 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
15:66 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
17:66 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
19:66 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
21:66 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
61:54 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
78:66 warning 'substring' is a possible misspelling. PostHogBase.Spelling
79:94 warning 'substring' is a possible misspelling. PostHogBase.Spelling
167:165 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
169:68 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
contents/tutorials/filter-internal-users.mdx — 0 errors, 7 warnings, 0 suggestions
Line Severity Message Rule
17:66 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
19:66 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
21:66 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
23:66 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
25:66 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
27:66 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
60:30 warning Use 'PostHog' instead of 'posthog'. Vale.Terms

@github-actions

Copy link
Copy Markdown
Contributor

Bundle report

Total JS (gzip)

6.73 MiB (no change)

Eager graph (modules shipped in each entrypoint's initial chunks)

Entrypoint Eager size Budget Modules
app 16.15 MiB (no change) report-only 1970
Largest modules in the app closure
Module Size
./src/data/mcp-tools.json 883.1 KiB
css ./node_modules/.pnpm/css-loader@5.2.7_webpack@5.101.3/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[1]!./node_modules/.pnpm/postcss-loader@4.3.0_postcss@8.5.6_webpack@5.101.3/node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[2]!./src/styles/global.css 743.0 KiB
./src/components/Stickers/Stickers.tsx 696.4 KiB
./node_modules/.pnpm/@radix-ui+react-icons@1.3.2_react@18.3.1/node_modules/@radix-ui/react-icons/dist/react-icons.esm.js 481.4 KiB
./node_modules/.pnpm/rehype-raw@7.0.0/node_modules/rehype-raw/lib/index.js + 29 modules 395.1 KiB
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.cjs.js 364.8 KiB
./src/hooks/useCustomers.tsx + 54 modules 355.1 KiB
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.es.js 354.8 KiB
./node_modules/.pnpm/react-markdown@8.0.7_@types+react@16.14.66_react@18.3.1/node_modules/react-markdown/lib/react-markdown.js + 88 modules 351.4 KiB
./node_modules/.pnpm/cloudinary-core@2.14.0_lodash@4.17.21/node_modules/cloudinary-core/cloudinary-core.js 281.9 KiB
./src/components/ProductComparisonTable/index.tsx + 120 modules 278.6 KiB
./src/components/SearchUI/index.tsx + 87 modules 271.9 KiB
./node_modules/.pnpm/d3@7.9.0/node_modules/d3/src/index.js + 208 modules 247.4 KiB
./src/components/Pricing/PricingSlider/Slider.tsx + 87 modules 239.9 KiB
./gatsby-browser.tsx + 43 modules 225.0 KiB

Eager-graph budgets are report-only until a baseline is established. Sizes are gzip of public/**/*.js; eager size is webpack module source bytes for the modules actually shipped in the entrypoint's initial chunks (post-tree-shake).

@github-actions

Copy link
Copy Markdown
Contributor

Hey @thmsobrmlr! This docs PR was generated for you by an agent. You're responsible for reviewing and merging it into production.

  1. Review and approve the PR
  2. Merge the PR
    a. Check the preview env and CI build and merge it yourself
    b. Enable auto-merge if you're confident in the changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

0 participants