Skip to main content
New Idea

FreshService objects as StatusPage subscribers

Related products:Freshservice
  • August 27, 2024
  • 3 replies
  • 50 views

Brad_Bazley
Apprentice
Forum|alt.badge.img

Hey there,

We’re so close to moving to StatusPage from a competing product, but subscriber management is our remaining roadblock.

Current state: Subscribers must be manually added or imported via CSV to StatusPage

Desired state: FreshService objects can be set as subscribers for a Service or Service Group, e.g.

  1. Agents
  2. Requesters
  3. Departments
  4. Requester Groups
  5. Roles
  6. Locations & location hierarchies

This would enable users to be dynamically included in Status Alerts at time of provisioning, instead of requiring an additional (heavily manual) provisioning step for each user’s own service alert needs.

This would also minimize the risk of accidentally adding external recipients for private Status Page sites, as the subscriber identity & contact details would be managed centrally within FreshService.

 

Thanks for all you do!

 

Brad at Material

3 replies

Forum|alt.badge.img+2
  • Contributor
  • October 15, 2024

Hello,

we would like to have the status page activated in the next few weeks, but we are still having problems with user management.

Currently, despite SSO, the user has to enter the email address when opening the status page. Why is this necessary? We don't want to publish the page completely without registration, but it should be possible to log in via SSO without having to additionally enter the email address!
Furthermore, it would be great if requesters or agents were automatically created in the status page. For example, based on the requester groups.


Forum|alt.badge.img+4
  • Skilled Expert
  • August 7, 2025

Dynamic subscriber groups could be SO nice to have :) 


AbominableSnowmin
Contributor
Forum|alt.badge.img+5

Great suggestion.  When using FreshService within companies, this is must-have manageability.  👍👍👍