# Beacon-only docs site behind login

> Keep the docs archive off a public site until logged-in users can reach it through Beacon, so onboarding and support answers stay usable without turning unfinished docs into public scenery.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/beacon-only-docs-site-behind-login/
- Source: [docs.helpscout.com](https://docs.helpscout.com/article/1329-control-access-to-docs-using-beacon)
- GrowthDex source hub: [Help Scout Docs](/sources/help-scout-docs-docs-helpscout-com/)
- Last checked: 2026-05-28
- Rarity: rare
- Budget: medium
- Channels: Support, Product, Onboarding
- Stages: customer education, self-serve support, access control, brand trust
- Key metric: Help Scout lets teams hide the Docs site entirely and expose articles only through Beacon for signed-in users

## Why this can grow

A lot of product docs are most useful to active customers, not to strangers. Help Scout gives teams a tighter middle ground than choosing between a fully public site and no self-serve help at all. You can keep Docs visible only through Beacon, require the customer to be signed in, and still let the product point users straight to the answer while they work. That keeps support content helpful without forcing every early or account-specific article onto the open web before it earns the right to be there.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where beacon-only docs site behind login can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Product channel.
3. Use the evidence from docs.helpscout.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Help Scout says teams can restrict Docs access to logged-in users and show the knowledge base only inside Beacon instead of on a public Docs site.

## Adjacent tactics in the same lane

- [Availability-gated docs chat with message fallback](/growth-ideas/availability-gated-docs-chat-with-message-fallback/) - same source, 1 shared channel, 2 shared stages
- [Customer-facing docs on a brand subdomain](/growth-ideas/customer-facing-docs-on-brand-subdomain/) - same source, 1 shared channel, 1 shared stage
- [Article-to-Beacon contact link at the point of confusion](/growth-ideas/article-to-beacon-contact-link-at-point-of-confusion/) - same source, 1 shared channel, 1 shared stage
- [Internal runbook collections feeding Beacon AI](/growth-ideas/internal-runbook-collections-feeding-beacon-ai/) - same source, 1 shared channel

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The docs page should know when to finish the job and when to hand off](/blog/the-docs-page-should-know-when-to-finish-the-job-and-when-to-hand-off/) - support-led growth, brand trust, technical SEO

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.