Managing multiple status pages
As your product or organization grows, a single status page often isn't enough. You might need separate pages for different products, brands, or customer segments, each with its own components, subscribers, and incident history.
Depending on the status page platform you use, managing those pages separately can become difficult. Subscribers end up juggling multiple subscriptions, admins lose visibility across pages, and during an outage, coordinating updates across several disconnected pages adds complexity and room for error.
This is a comparison of how Sorry™ and Atlassian Statuspage approach multi-page management, covering the setup experience, subscriber management, and admin workflows.
Functionality comparison
| Feature | Sorry™ | Atlassian Statuspage |
|---|---|---|
| Multi-page dashboard | Single view of all pages and Collections in your account | No equivalent, pages are accessible via a static dropdown |
| Active incident/maintenance visibility | A status badge on each page in the dashboard shows active incidents or maintenance at a glance | No at-a-glance status indicator; you need to navigate into each page individually |
| Subscriber count per page | Visible directly from the multi-page dashboard | Only visible by navigating into each page and clicking through to the subscribers section |
| Public/private page indicator | Visible directly from the multi-page dashboard | Not visible from the page list |
| Create a multi-page Collection | Built-in functionality to create a Collection in seconds, with example pages auto-populated so you can preview the experience before going live | No native equivalent; requires custom development and design work |
| Subscriber management across pages | Single subscription profile where subscribers manage all their page preferences from one place without re-entering their email or clicking magic links | Per-page subscriptions require subscribers to navigate to each page individually, request a magic link, and manage preferences separately |
| Dynamic subscriber view | Personalised view showing pages a subscriber is subscribed to at the top; pages with active incidents automatically surface above the rest | All pages displayed the same way regardless of subscription status or active incidents |
| Team access control | Controlled directly within the Sorry™ UI – team members can be limited to specific Collections and pages, regardless of plan | Available on Business plan and above only; managed through Atlassian Admin (separate interface), not within Statuspage itself |
| Billing management | Managed directly within Sorry™ | Managed through the Atlassian Admin portal, separate from Statuspage |
Sorry™ offers a dynamic multi-page dashboard
When you log in, you're taken to the most recent page you were editing. From there, navigating to other pages is straightforward. The status page dashboard gives you a complete overview of all the pages you have access to in a single view.
From this dashboard, you can see at a glance whether each page has an active incident or maintenance notice, whether it's public or private, and its total subscriber count.
This dashboard also lets you create a new page, edit the page name, delete a page, or move a page into a Collection — all without leaving the screen. You can also quickly navigate to the admin view or page view.
This screen provides a practical, functional overview that keeps everything easily accessible without needing to jump between pages or click through numerous options to find what you need. Teams that manage multiple status pages find this extremely helpful.
Hosting.com manages incident communication for 32 brands with Sorry™.
Read the case study →Atlassian offers a static multi-page drop-down
When you log in to Statuspage, you're also taken to the last page you were working on. Switching between pages is simple using a dropdown menu. This is functional, but it's also where the multi-page overview ends.
There's no dashboard that shows all your pages in one view. To check subscriber counts, you need to navigate to each page individually and click through to the subscribers section. There's no at-a-glance indicator of whether a page has an active incident, so if something is wrong on one of your other pages, you won't know until you navigate there directly.
It's also worth noting that pages can span multiple organizations in Statuspage, which can create confusion about where a particular page lives and who has access to it. Billing is managed separately through the Atlassian Admin portal rather than within Statuspage itself, adding another layer of context-switching for admins.
For teams managing a handful of pages with a small team, this is workable. But for teams that need visibility across multiple pages at once, staying on top of things requires more manual effort.
Sorry™ Collections give you a native way to aggregate multiple pages into a unified view
Sorry™ has a dedicated feature for managing multiple status pages called Collections. This is a powerful feature for teams that manage a large number of products or services and need an extra layer of organization while providing a seamless subscriber experience.
A Collection groups multiple individual status pages into a single, unified view. You get one branded domain, your customers get a single subscription profile, and your team has one place to manage all status pages seamlessly.
Creating a new Collection in Sorry™ is simple. Sorry™ provides an intuitive UI for moving existing pages into a Collection or adding new pages to a Collection.
Collections were built to be flexible and scalable, making it easy for teams to update their pages while improving the user experience for customers and stakeholders.
Creating a Collections equivalent in Statuspage requires custom development
Statuspage doesn't have a native equivalent to Collections. There's no built-in way to group pages into a unified view, create a shared domain across multiple pages, or give subscribers a single place to manage all of their notifications. If you want a unified view in Statuspage, you'll need to invest in custom development and design work.
<!-- JIRA -->
<a href="https://jira-software.status.atlassian.com/" target="_blank"
class="page-status-container span6" id="page-7yh3h3y0c0x1">
<div class="logo">
<img src="https://dam-cdn.atl.orangelogic.com/AssetLink/a4062k03432374vok1upng5m27k121x8.svg">
</div>
<div class="status-info">
<div class="product-name">Jira</div>
<div class="skeleton-status"></div>
<div class="stub-for-status"></div>
</div>
</a>
<!-- JIRA SERVICE MANAGEMENT -->
<a href="https://jira-service-management.status.atlassian.com" target="_blank"
class="page-status-container span6" id="page-pv54g7ltsc24">
<div class="logo">
<img src="https://dam-cdn.atl.orangelogic.com/AssetLink/c100stu4gb6xcvw2jp1a4f78447igxx4.svg">
</div>
<div class="status-info">
<div class="product-name">Jira Service Management</div>
<div class="skeleton-status"></div>
<div class="stub-for-status"></div>
</div>
</a>For teams managing a few pages with less complex needs, Statuspage's multi-page support might work. But for teams that need a cohesive experience across multiple pages — for both admins and subscribers — the gaps become obvious and hard to work around. Scalability quickly becomes an issue.
The subscriber experience
Managing and administering multiple status pages is one thing. But you also need to consider the subscriber experience. If staying informed requires effort — multiple subscriptions, separate magic links, jumping between URLs — some subscribers simply won't bother. Here's how each tool handles it.
The subscriber experience in Sorry™
All notification channels in Sorry™ (email, SMS, Slack) are tied to a single subscriber account, making it easy to manage any notifications a subscriber receives.
With Sorry™ Collections, subscribers manage all of their page preferences from a single subscription profile. When someone subscribes to a Collection, they can select which pages they're interested in, then drill into each page to tailor their component-level preferences all in one place. There's no need to re-enter their email or request a new magic link as the system already recognizes their profile.
The view is also personalized on the Collection page to show the subscriber's already-subscribed pages at the top. This means subscribers immediately see what's relevant to them without having to scan through every page in the Collection.
The subscriber experience in Atlassian Statuspage
In Statuspage, each subscription channel is disjointed, meaning you have to modify it independently. Statuspage also handles subscriptions on a per-page basis. If a subscriber wants updates from multiple pages, they need to navigate to each page individually, enter their email, and wait to receive a magic link to confirm their subscription.
What matters more is that they have to repeat this process for every page they want to subscribe to. There's no unified view and no single subscriber profile that spans multiple pages.
Admin access controls
As your team grows, you'll need more granular control of who can manage which status pages. You might want support staff to update incidents on a specific page without giving them access to other pages.
Sorry™ offers RBAC (Role-Based Access Control) on all plans. Atlassian Statuspage restricts RBAC to the Business tier ($399/mo) or higher.
Furthermore, any user invited through the Atlassian Admin is granted full access to all pages by default, so you have to manually restrict them afterward. Permissions are also managed in a separate Atlassian Admin portal rather than within the Statuspage UI.
RBAC and user management aren't straightforward for anyone unfamiliar with the broader Atlassian ecosystem.
Built for multi-page management from the start
For growing teams, managing multiple status pages is a daily routine. Sorry™ was designed with that in mind.
From the multi-page dashboard that gives you a complete overview of your account, to Collections that bring multiple pages together into a single, seamless experience for admins and subscribers alike, every part of the multi-page experience in Sorry™ is intentional.
Atlassian Statuspage works well as a single-page tool or when managing a handful of separate pages. But when it comes to managing multiple pages at scale, the limitations become visible quickly: no unified dashboard, no native Collections functionality, and admin tools scattered across Atlassian portals.
If managing multiple status pages is a core part of how your team operates, it's worth using a platform that treats it as a first-class feature rather than an afterthought.
Additional resources
See how Sorry™ can help you manage multiple status pages
Want to see how easy it is to manage multiple status pages in Sorry™? Reach out to schedule a demo, or sign up for a free trial.