Forum Discussion
PatrickPatrick
Qrew Member
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
MCFNeil
8 years agoQrew Captain
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.
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.