Early access of Private Status Pages in Jira Service Management Enterprise

[#1]

👋 Hi Community,

We've been listening — and we know that not every status update is meant for the world. Sometimes you need to keep your customers, employees, or partners in the loop without publishing to a public page.

Today, we're excited to open the Early Access Program (EAP) for Private Status Pages in Jira Service Management Enterprise. 🎉

What are Private Status Pages?

Private Status Pages let you share real-time incident updates and service health information with only the people you choose - your internal teams, customers under NDA, or a specific group of partners.

Why we built this ?

Public status pages are great for transparency. But many of you have told us that:

• 👥 You have internal services (HR tools, finance systems, internal dev platforms) where status should only be visible to employees.

• 🤝 You serve enterprise customers who require a dedicated, authenticated status page

• 🛡️ You operate in regulated industries where incident details cannot be shared publicly for compliance reasons.

• 🔄 You're paying for a standalone statuspage tool just to get this capability — and would prefer it native to JSM.

What you'll get in the EAP?

• ✅ Create one or more private status pages, scoped to authenticated audiences

• ✅ Add components, post incidents and link directly from Jira service management incidents

• ✅ Control access via your existing atlassian permissions and groups

• ✅ Branded pages with your logo, colors and components

• ✅ Direct access to our product team for feedback, feature requests, and the opportunity to help shape the General Availability product experience

🎟️ How to join the Early Access Program?

👉 Sign up here. Spots are limited — we're onboarding customers in waves to make sure every participant gets the support they need over the next few weeks.

Who can join:

• You're on the Service Collection Enterprise plan

• You have at least one active incident management use case

• You're willing to share feedback through a short survey and an optional 30-min interview

⚙️ How to set up your Private Status Page ?

Once you're accepted into the EAP, here's how to get up and running:

Step 1: Enable Private Status Pages in your site

1. Open Jira Service Management → Operations → Status pages

2. You'll see a Private Status pages unlocked when you click on “Create” button

Step 2: Create your first private page

1. Click Create 

2. Give your page a name (e.g., "Internal Tools Status" or "Enterprise Customer Status — Acme Corp")

3. Choose a URL (e.g., internal-tools)

4. Confirm with the  Create button

Step 3: Add your components

1. Go to Components on your new page

2. Add the services you want to track (e.g., "Internal Wiki", "VPN", "Build System")

3. Group related components together for clarity

Step 4: Brand it and share the link

1. Under Appearance, upload your logo and choose your brand colours

2. You can even customise branding using HTML/CSS

Step 5: Set who can access it

1. In your new page settings, go to “Advanced Setting”

2. Go to Access control

3. Select the Atlassian groups who should be able to view the page

4. Click on Save to confirm the Atlassian groups mapped to the page

Step 6: Publish your private status page

1. Click Publish on the top right

2. Review the details and confirm with "Publish" button to make the page live.

Step 7: Send incident updates to the private status page

1. Go to your project, select any Open incident

2. Navigate to Status pages and click on “Add Status page”

3. Select the Private Status Page you published

4. Fill all the necessary fields, update the component status and click on “Send Update”

With all the details above, you’re now ready to set up and start using Private Status Pages in Jira Service Management Enterprise!

👉 Want to explore other stakeholder communication capabilities launched in the past, view them here!

[Josh]

Can't wait to try this, @Deeksha !