Decouple Edge mobile pin from V5000 pin

When integrating voice and Edge in the Viking configuration, creating an Edge mobile pin also forces a pin when logging into the V5000. This may be desirable for some customers but it was seen as an issue at PIH. Edge mobile pins are much more commonly used than V5000 pins. Customers need the ability to configure an Edge mobile pin without impacting the experience on the V5000 badge.

  • Guest
  • Oct 8 2025
  • Clarification requested
V5000
  • Attach files
  • Admin
    Rishi Purohit commented
    5 Nov 12:42am

    Micah -

    Thanks for providing some additional background here, especially the notion that this may be a bug fix vs. a new feature. This information is great for me to use to circle back with the team.

    We're kicking off a renewed Aha process (to be rolled out in the coming weeks) and I'm doing a little board management in the meantime.

    More to come - thanks for the info!

    Rishi

    Attachments Open full size
  • Guest commented
    29 Oct 04:17pm

    Rishi,

    Thank you for following up on this! It was identified at PIH (EU IHCPIHZ CA01) that setting the pin on edge mobile forces the user to enter the pin on smartbadge. We need to ensure the pin can be set on Edge mobile independently from the pin requirement on smartbadge. It is reasonable to ask a smartphone user to enter a pin after a certain period of inactive time. It is NOT reasonable to ask a smartbage user to do the same thing, as the smartbadge is on their person at all times and is less likely than a smartphone to be left unattended. @Fasching, Blake mentioned on a call that this might not have been working as expected - in other words, this might be a bug fix rather than a feature request. So I do hope he can chime in and keep me honest on that. I'm providing the PIH related cases for reference, but please note that the only reason this is "resolved" at PIH is because they still have the edge mobile pin disabled. They do want to reenable the mobile pin without impacting their smartbadge users.

    * Initial SF case: 00534464
    * Escalation SF case: 00534482
    * Jira: CASE-5442

    Regards,
    Micah
    415-686-0916

    Attachments Open full size
  • Admin
    Rishi Purohit commented
    28 Oct 09:36pm

    For Micah:

    • We are looking to understand the workflow that leads to this ask. Are there customer examples for this?

    For Portfolio:

    • Understand why this functionality was designed as a part of the Viking experience

    Attachments Open full size

Related ideas