Customizing or building features on top of Enterprise Status Page

[Harsh Modi]

Hi, can we build required features (for example: searching components on the page) on top of Enterprise offering? Thanks!

[Jesse Klein]

Hello there,

This is Jesse from the Statuspage support team. Welcome to the community and thanks for your question around custom features.

If you were on an enterprise plan (business plan would also work), you would have access to custom CSS, HTML, and JS. You would be able to utilize these to add other features on your page.

One important thing about custom code that you should be aware of. Because of this being a custom implementation from your side, we cannot comment on how to get your code to work in a particular way. You can, however, check this article out for inspiration: https://support.atlassian.com/statuspage/docs/css-and-javascript-snippets-for-customizations/

Hope that helps you out and I hope you have a great day!

Regards,
Jesse

[Harsh Modi]

Hi Jesse, I'd like to confirm if the customizations are limited to the mentioned ones on the given link? 

[Jesse Klein]

Hello,

The customizations are not limited to just the ones above. Those are just examples of things that are possible. There's quite a bit of freedom to what you can do using the custom code.

One of my favorite examples to show off is: https://status.newrelic.com/

They have a very nicely customized page that was done with custom code.

Hopefully that gives some more inspiration on what can be done!

Regards,
Jesse

[Harsh Modi]

thanks for the responses! Also, we do have a requirement of having status page for internal and external audience. Would this require us to buy 2 different status pages or can be done in one? 

Example:

1. Internal audience sees more components than external.

2. Managing notifications for internal vs external audience by the user.

Thanks!

[Jesse Klein]

Hello again,

Having internal and external audiences would typically require having two pages. If you know exactly who your internal and external audiences were, then you might consider an audience specific page: https://support.atlassian.com/statuspage/docs/what-are-audience-specific-pages/

This would require logins for each user, however, so that might not be viable for your use case. In that case, two pages would make sense.

Hopefully that helps!

Regards,
Jesse