💡 Feature Requests

Enable users that have signd up via SSO to sign in via the standard sign-in page.

In the Members page - it would be great to be able to filter by Role - so that we can routinely audit/check who can perform which actions in the platform. Thanks!

Just as we can deactivate the notifications on start and on end of a maintenance window, we would like to deactivate the automatic updates "Started" and "Resolved" in the status page. We would rather inform manually about the start/end of a maintenance, since there can be small variations in time to the scheduled start and end time.

Being able to order the user list by name, date, role ... just with a click :)

The admin UI allows adding HTTP headers for the Statuspal requests. However, the HTTP headers are restricted to a predefined list of headers, and it makes it impossible to add a custom header via the admin UI. If a custom HTTP header is added via the Statuspal API, the new header shows up in the admin UI. However, the UI renders the form field empty for the key, but with the intended value for the value field. Please see the screenshot. If the admin UI form is saved, the custom HTTP header added via API will likely to be reset or removed altogether, simply because the header name is not listed in the pre-defined list. Please allow adding custom HTTP headers using the admin UI.

Just as the "incident types" can be customized, we would like to have the possibility to customize "update types". Right now there are only two update types for scheduled maintenance: update and monitoring. We would like to create further types. The same goes for major incidents.

It'd be great to be able to search through subscribers with partial values, such as half their email

Allow dynamic notification sending based on a metadata field on subscribers. General context is we have clients that use certain features, and if an issue arises for those particular features, we would like to signal those users. The subscription groups would be overly complicated to use for this particular cases. Would be nice to have some matching rules used with a metadata field on the subscription entity.