Can a notification have a button to open a specific request but require recipient to log in before editing the request?

  • 1
  • 2
  • Question
  • Updated 2 years ago
  • In Progress
Currently we send notifications to Approvers that include a button to open the specific Request needing review. When the button is used, the correct request opens, but if the reviewer now edits and Approves the request, they are recorded as "Anonymous" in the Request. Is there a way, when using the button, to force the Appover to log-in to that Request before they can edit it?
Photo of Patrick

Patrick

  • 40 Points

Posted 2 years ago

  • 1
  • 2
Photo of Matthew Neil

Matthew Neil

  • 31,478 Points 20k badge 2x thumb
You are using an "everyone on the internet" user in the app.  In order to force a QB login, you will need to restrict the edit permissions for that role.

This might affect other reasons you have the open to the internet role, but you know your situation the best.
Photo of Patrick

Patrick

  • 40 Points

Matthew, thank you for the reply. To clarify something, while we do have in our User Table an "everyone on the internet" user. The emails (with a link to a request) that go to actual users of the APP (their Notice's have a "Permission Type" of  "Recipient" not "Open") have this problem too.

Is it simply having a User "everyone on the internet" in the table, that will prevent even actual, individual Users from being required to log-in before doing edits?

Thanks, Pat

Photo of Matthew Neil

Matthew Neil

  • 31,478 Points 20k badge 2x thumb
Correct,  If they can 'see/edit' it without logging in, the browser wont force them.

Maybe make a custom URL that gets sent in the email, that directs them to the login page first with the 'nexturl' being the actual record in question.