# Audience-specific status page by cluster or tier

> Split the status experience by customer group, shard, or plan so each audience only sees the components and alerts that actually matter to them.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/audience-specific-status-page-by-cluster-or-tier/
- Source: [support.atlassian.com](https://support.atlassian.com/statuspage/docs/what-are-audience-specific-pages/)
- GrowthDex source hub: [Atlassian Statuspage Docs: What are audience-specific pages?](/sources/atlassian-statuspage-docs-what-are-audience-specific-pages-support-atlas/)
- Last checked: 2026-05-29
- Rarity: epic
- Budget: medium
- Channels: Support, Lifecycle, Sales
- Stages: enterprise, customer segmentation, incident comms, trust


## Why this can grow

The broad status page gets noisy fast when the product serves different clusters, tenants, or internal teams. Atlassian's audience-specific pages are useful because they let a company choose who can view a page, which components they see, and which notifications they can receive. That changes the page from a generic incident billboard into a scoped communication tool. Customers get clearer answers, support gets fewer false alarms, and high-value accounts stop wondering whether a problem on another shard applies to them.

## 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 audience-specific status page by cluster or tier can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Lifecycle channel.
3. Use the evidence from support.atlassian.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

Atlassian Statuspage says audience-specific pages can be used when customers are hosted on single-tenant infrastructure or grouped on clusters or shards, with permissions controlling what each group can view and subscribe to.

## Adjacent tactics in the same lane

- [Customer-specific status page for dedicated infrastructure](/growth-ideas/customer-specific-status-page-for-dedicated-infrastructure/) - 2 shared channels, 2 shared stages
- [Private roadmap portal with domain-based access](/growth-ideas/private-roadmap-portal-with-domain-based-access/) - 1 shared channel, 2 shared stages
- [Atlassian Marketplace privacy and support completeness](/growth-ideas/atlassian-marketplace-privacy-and-support-completeness/) - 1 shared channel, 2 shared stages
- [Dedicated status domain before first incident](/growth-ideas/dedicated-status-domain-before-first-incident/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The status page should answer who is affected before support opens](/blog/the-status-page-should-answer-who-is-affected-before-support-opens/) - brand trust, support-led growth, operations

## Advisory

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