How to hide a component at StatusPage dashboard
Asked by irazubaiev:

I'm looking for an option to hide specific component on StatusPage, so it will not be visible on dashboard, and it will not be possible to subscribe to it. However I want this component to be accessible by API with abilities to create an incident, subscribe or update its status. Currently I don't see such option in documentation but If there is any workaround or alternative approach to achieve it - please respond, any help is welcome.


Answers:
author: Mubeen Mohammed
body: Hello [@irazubaiev](/t5/user/viewprofilepage/user-id/5146617)

Thank you for contacting the Atlassian community! this is Mubeen.

The ability to hide a component from the external Statuspage is possible when you are creating or updating the component using the API request.  

By following the API documentation ([create a component](https://developer.statuspage.io/#tag/components) or [update a component)](https://developer.statuspage.io/#operation/patchPagesPageIdComponentsComponentId) when you send the request with **"only_show_if_degraded": true** then the component will only be visible internally on the [admin page](https://manage.statuspage.io) and will be hidden from external users who have access to the page URL. However, as the name suggests if the Status of this component is changed to anything other than Operational then it will be visible externally too.

I hope the information provided is helpful. You can test the functionality with the suggested options and let us know if you have more questions. I will be happy to assist.

Regards

Mubeen Mohammed

Cloud Support Engineer

comments: author: Antony Swift
body: Hello [@Mubeen Mohammed](/t5/user/viewprofilepage/user-id/4779601)

Please can a new feature request be added for it to be possible to hide components from within the statuspage UI for both public and private pages.

Currently i cant do this, so any changes, or preparation i want to make to improve our public page and it's structure becomes immediately visible, which could cause confusion with our customers.

Kind regards


author: Darryl Lee
body: [@Antony Swift](/t5/user/viewprofilepage/user-id/5173335) as [@Mubeen Mohammed](/t5/user/viewprofilepage/user-id/4779601) suggested in the most recent comment, it is do-able and that API endpoints are available for both Public and Private pages.

Please kindly check to see if the suggested approach works by sending API requests to update your current components or create new ones.

Thank you.

Best regards,   
Darryl Lee  
Support Engineer, Atlassian


author: Antony Swift
body: Hi Darryl,

Thank you. I had understood already that API endpoint were available. My request was for that to also be included within functionality in the UI, such as with a checkbox to hide for each component.

Kind regards

Antony


author: Darryl Lee
body: Hi [@Antony Swift](/t5/user/viewprofilepage/user-id/5173335),

Appreciate your clarification and I understand your point.

I have found an existing feature request to make the "hide component" available directly on the UI.

The feature request ticket is **STATUS-112**.

**Please be aware of that all the feature requests for Statuspage are logged on our internal system, our customers DO NOT have visibility to check those tickets.**

Therefore, we will keep you posted.

Please also note that the ETA is currently unavailable because our Product team reviews all Feature Requests (FR) jointly and gives priority to implementing those with the highest demand. Any FR will take time to complete because it must go through Design, Development, Testing, and rolling out to Production.

*** ** * ** ***

**Appreciation**  
We greatly appreciate your thoughts on how we might make Statuspage better; it really helps.  

In the meanwhile, we apologize for this inconvenience and frustrations this unsatisfactory functionality has created.

Best regards,   
Darryl Lee  
Support Engineer, Atlassian


author: John W
body: Does the "only_show_if_degraded": true parameter work on Audience-specific pages? I have it enabled but the component is still showing in the dashboard.


author: Talar Pavlovic
body: Hi there John,

Thanks for writing to Community! Talar here from the Atlassian Statuspage Support team.

I've done some testing and spoken to our Engineering team - it seems to have stumbled upon a bug. Thank you for reporting it, I have created an internal bug report for our Engineering team to investigate + fix this.

Regards,  
Talar


author: John W
body: Thanks Talar for the response. Let me know if/when there are any updates on that bug report.


author: Mubeen Mohammed
body: Hello John,

Thank you so much for your feedback, As Talar mentioned a BUG request has been created and STATUS-662 is the ticket ID for your reference. Unfortunately, the Bug ticket doesn't provide public access to our customers, we will keep you posted.

Thank you very much for your feedback on this issue.

Should you have any further inquiries or requests, please reach out to the Statuspage Support Team via [this link](http://issue%20summary%20%20after%20the%20unsubscription%20of%20sms%20and%20trying%20to%20re-subscribe%20with%20the%20same%20phone%20number%20after%20a%20couple%20of%20minutes%2C%20the%20subscription%20page%20does%20not%20respond%20at%20all.%20%20on%20the%20sp%20admin%20to%20manually%20add%20this%20number%20to%20the%20sms%20subscription%2C%20an%20error%20will%20throw%20even%20though%20the%20number%20isn%27t%20showing%20on%20the%20sms%20subscribers%20list:%20%20the%20email%2C%20phone%20information%2C%20or%20endpoint%20provided%20is%20already%20subscribed%20to%20updates.%20%20%20steps%20to%20reproduce%20go%20to%20subscribe%20to%20a%20statuspage%20via%20sms%20and%20complete%20the%20verification.%20with%20the%20same%20number%2C%20proceed%20to%20unsubscribe%20to%20this%20statuspage.%20after%20a%20couple%20of%20minutes%2C%20try%20step%201%20again.%20on%20the%20admin%20page%20of%20this%20statuspage%2C%20try%20to%20manually%20add%20this%20number%20to%20the%20sms%20subscribers%20list.%20expected%20results%20%20the%20same%20phone%20number%20should%20be%20able%20to%20resubscribe%20to%20that%20statuspage%20after%20the%20un-subscription%20has%20proceeded.%20%20actual%20results%20%20after%20the%20unsubscription%20of%20sms%20and%20trying%20to%20re-subscribe%20with%20the%20same%20phone%20number%20after%20a%20couple%20of%20minutes%2C%20the%20subscription%20page%20does%20not%20respond%20at%20all.%20%20on%20the%20sp%20admin%20to%20manually%20add%20this%20number%20to%20the%20sms%20subscription%2C%20an%20error%20will%20throw%20even%20though%20the%20number%20isn%27t%20showing%20on%20the%20sms%20subscribers%20list:%20%20The%20email,%20phone%20information,%20or%20endpoint%20provided%20is%20already%20subscribed%20to%20updates.%20%20Workaround%20%20Need%20to%20wait%20after%20a%20long%20while./), and we will be happy to help.

Regards

Mubeen Mohammed

Cloud Support Engineer


author: Christian Klemens
body: Hello Atlassian Team,

please add us as an additional requester to ticket STATUS-112